Ticket #133 (closed defect (bug): fixed)

Opened 8 years ago

Last modified 8 years ago

Conditional GET still sends data after 304 Not Modified

Reported by: kelson Owned by: matt
Priority: normal Milestone:
Component: General Version: 1.2
Severity: minor Keywords:
Cc: kelson, hugo

Description

If Wordpress determines that the output has not changed since the last update, it does generate a "304 Not Modified" response - but it still sends the data, defeating the purpose and wasting bandwidth.

Change History

comment:2   hugo — 8 years ago

Tried the suggested move of the exit out of ifs and it works right. Only problem I still see is that Last-Modified date is compared exact and not relative. This only works if clients send in the content of the Last-Modified header they received from the server with their If-Modified-Since header. If they use a system date of the stored (cached) file, they will often send in slightly different dates and exact matching won't work. So to really gain from the Last-Modified header, you would need to use relative comparison.

comment:3   matt — 8 years ago

  • Owner changed from anonymous to matt
  • Status changed from new to closed
  • Resolution changed from 10 to 20

comment:4   matt — 8 years ago

All fixed up. :)

Note: See TracTickets for help on using tickets.