WordPress.org

Make WordPress Core

Opened 19 months ago

Last modified 7 months ago

#19466 new enhancement

Last-Modified HTTP header not just for feeds

Reported by: sergey.s.betke@… Owned by: sergey.s.betke@…
Priority: normal Milestone: Awaiting Review
Component: General Version: 3.3
Severity: normal Keywords: dev-feedback
Cc:

Description

Wordpress write HTTP Last-Modified, ETag headers just for feeds (class-wp.php, send_headers). And support If-Modified HTTP request header just for feeds. Wordpress 3.3 doesn't support HTTP 1.1 Cache-Control header.
The best solution - support HTTP cache-control headers and for html output (full blog). But If-Modified HTTP request header (304 responces) for site support optionally (some not-ajaxed widgets and plugins will show wrong information without page reloading).

WordPress version

Latest WordPress files - 3.3-RC2-19567

Attachments (1)

19466.diff (921 bytes) - added by sergey.s.betke@… 19 months ago.
patch for full support Last-Modified, ETag, If-Modified HTTP headers

Download all attachments as: .zip

Change History (2)

sergey.s.betke@…19 months ago

patch for full support Last-Modified, ETag, If-Modified HTTP headers

comment:1 brokentone7 months ago

First -- I'm just your average community member, no one important.

I have similar desires to expand this functionality, and I've also had issues with the current application. It's far too brute-force, assuming that the only (and that every) time the site is updated is when a post or a comment is posted, and that the entire site is affected by such a thing. Applying the existing logic to every request would be a serious mistake. I've created another ticket with a more complete discussion of the matter - #22742

Note: See TracTickets for help on using tickets.