The proper functioning of XML jitlinks depends crucially on redirecting RSS feeds. Now, there doesn’t seem to be a huge consensus on how to redirect RSS feeds. I’ve chosen to use HTTP-level redirects, i.e. 3xx response codes in routing XML jitlinks to the right feeds. Ever since adding support for XML jitlinks yesterday, I’ve been noticing something screwy is going on with online RSS aggregators like Google Reader.
The native RSS support built into browsers like Internet Explorer recognizes and works with an XML jitlink just fine, but Google Reader doesn’t seem to honor 3xx redirects. This means that after a Google Reader user subscribes to an XML jitlink, they won’t seamlessly receive updates (say from Twitter) on that subscription. I’ve been noticing similar behavior with Bloglines as well.
WhenGuard is currently responding with 3xx redirects for all feed readers other than Google Reader and Bloglines. For these two online feed readers, WhenGuard is returning a 200 and proxying the true content into the response stream. If anyone has had success with Google Reader and redirects (temporary or permanent), I’d appreciate hearing from you from the feedback link. I don’t know what the solution is just yet, but I thought I’d put a note out there to tell people that I am aware of the problem and am trying to find a solution.
Until next time,