[wp-trac] [WordPress Trac] #13066: Last-Modified headers for individual comment feeds are incorrect
WordPress Trac
wp-trac at lists.automattic.com
Wed Apr 28 04:35:00 UTC 2010
#13066: Last-Modified headers for individual comment feeds are incorrect
--------------------------+-------------------------------------------------
Reporter: solarissmoke | Owner:
Type: defect (bug) | Status: new
Priority: low | Milestone: Future Release
Component: Feeds | Version: 3.0
Severity: normal | Keywords: dev-feedback
--------------------------+-------------------------------------------------
Comment(by solarissmoke):
Replying to [comment:2 dd32]:
> Its a trade off between bandwidth and server load, continuing to process
the request will require loading the rest of WordPress & parsing the
request & database fetches. all of which, would be pointless if no
comments have been posted.
True, but every time Wordpress sends a 200 response where 304 would have
done, we end up wasting both bandwidth and server load (because a full
load takes place anyway).
> * Leave as-is
I would suggest that even for semantic reasons the Last-Modified
information should reflect the state of the content being served (the 304
issue aside).
> * Make the comment check specify the post for the requests using a
manual SQL
As you say this would be a little messy for pagename requests etc. The
easiest option would be to do it after everything has loaded, at the
expense of server load.
I was also thinking whether it might be possible to cache (in the db) the
last-modified data for feeds, so that this could be accessed early in the
execution? That might be even more messy though.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/13066#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list