Opened 13 years ago
Closed 9 years ago
#19466 closed enhancement (maybelater)
Last-Modified HTTP header not just for feeds
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.3 |
Component: | Bootstrap/Load | Keywords: | |
Focuses: | 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)
Change History (4)
#1
@
12 years 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
patch for full support Last-Modified, ETag, If-Modified HTTP headers