RSS feeds reported as unmodified after publishing an entry
Posted: Sun Oct 04, 2009 7:19 pm
Hi,
I just discovered an oddness that I believe is a bug. Today I published a new entry in my blog. Looking at the webserver logs I noticed that all accesses to the feeds (like /feeds/atom10.xml) were answered with a HTTP 304 Document Unmodified response. I downloaded the XML and the new entry is included with
A trace of the network packets showed, that everybody is accessing the feed with a Modified-Since header that asks for updates since 2009-08-24 and my webserver happily responds with Document Unmodified. For the just published entry I find the following timestamps in the entries table (converted to readable output):
Looking at include/admin/entries.inc.php I believe the following is happening: I created the entry on August 24th. I edited it a couple of times as draft and used the clock button to adjust the time. But that only seems to have an effect on the timestamp and not the last_modified attribute. When I finally published the article today it is still marked as old in the database. In my opinion the last_modified attribute should be adjusted for every save operation as well. I looked into the 1.5 beta code (I'm still on 1.4.1) and it doesn't seem to have changed there. Maybe this could be fixed before 1.5 comes out?
Regards,
Stefan
I just discovered an oddness that I believe is a bug. Today I published a new entry in my blog. Looking at the webserver logs I noticed that all accesses to the feeds (like /feeds/atom10.xml) were answered with a HTTP 304 Document Unmodified response. I downloaded the XML and the new entry is included with
Code: Select all
<published>2009-10-04T15:31:00Z</published>
<updated>2009-08-24T18:25:26Z</updated>Code: Select all
timestamp | last_modified
--------------------+---------------------
2009-10-04 15:31:00 | 2009-08-24 18:25:26Regards,
Stefan