[ php-blog-Feature Requests-1588802 ] nocache for FeedBurner

Feature Requests item #1588802, was opened at 2006-11-01 11:12
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=542825&aid=1588802&group_id=75065

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: User functions
Group: Future Release
>Status: Closed
Priority: 1
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Garvin Hicking (garvinhicking)
Summary: nocache for FeedBurner

Initial Comment:
After lots of back-and-forth with FeedBurner support,
we discovered FeedBurner is not expecting the currently
implemented form of delta encoding for Serendipity's
RSS feed. Passing nocache on the GET line, per this
technote:

http://www.s9y.org/42.html

has resolved the issue for me personally, however
FeedBurner will probably not change its expectations in
the If-Modified-Since negotiation anytime soon.
Therefore, I propose adding:

if (isset($_SERVER['HTTP_USER_AGENT'])) {
    if(stristr($_SERVER['HTTP_USER_AGENT'],'feedburner')) {
         $_REQUEST['nocache'] = true;
   }
}

or equivalent (perhaps compile an array of User-Agent
strings that expect the full feed, not incremental
changes, but still use If-Modified-Since?) to the top
of rss.php for future releases.

The other option would be to investigate what
FeedBurner is expecting in its If-Modified-Since
negotiation (basically, I believe it wants just a 200
or a 304, not an incremental of new <item> entries
based on the date).

I worked with Eric Lunt (feed[NOSPAM]back at feedburner
dot c o m) on case# 36656 and he was extremely helpful.
I'm sure he'd be willing to chat with Serendipity devs
about this as well, since it is in everyone's mutual
best interest for Serendipity and FeedBurner to play
nice. :)

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2006-11-16 19:20

Message:
Logged In: YES 
user_id=1312539
Originator: NO

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Garvin Hicking (garvinhicking)
Date: 2006-11-02 03:20

Message:
Logged In: YES 
user_id=473563

Hi!

Thanks a lot for the suggestion to auto-set the nocache
option. I believe this is the most easy way to go.

Apart from that, sadly there is no unique way to deal with
the If-Modified stuff without either losing functionality or
losing RFC-compliance. :-(

I committed your workaround to the 1.1 SVN!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=542825&aid=1588802&group_id=75065

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV