Make WordPress Core

Opened 20 years ago

Closed 20 years ago

Last modified 20 years ago

#133 closed defect (bug) (fixed)

Conditional GET still sends data after 304 Not Modified

Reported by: kelson's profile kelson Owned by: matt's profile matt
Milestone: Priority: normal
Severity: minor Version: 1.2
Component: General Keywords:
Focuses: Cc:


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 (4)

#2 @hugo
20 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.

#3 @matt
20 years ago

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

#4 @matt
20 years ago

All fixed up. :)

Note: See TracTickets for help on using tickets.