Fixing Google’s Feedburner problem, and caching that half works

Lobsters Hottest News

Summary

The author shows how to bypass Google Feedburner's stale Atom feed by accessing the Blogger RSS feed with a `?redirect=false` parameter, restoring fresh Chrome Releases updates for their CCBot, and demonstrates that this feed partially supports `If-Modified-Since`/304 caching while Feedburner itself remains broken.

<p><a href="https://lobste.rs/s/nbtm5j/fixing_google_s_feedburner_problem">Comments</a></p>
Original Article
View Cached Full Text

Cached at: 11/22/26, 01:37 PM

# Fixing Google’s Feedburner problem, and caching that half works Source: [https://joshua.hu/fixing-google-feedburner-cache-problem-atom-rss](https://joshua.hu/fixing-google-feedburner-cache-problem-atom-rss) ## Getting around Feedburner In a[previous post](https://joshua.hu/wtf-google-feedburner-cache-problem-atom-rss), I talked about how Google’s[Chrome Releases blog](https://chromereleases.googleblog.com/)was serving stale results on its Atom feed, and had set up a redirect from its RSS feed \(which was serving up\-to\-date results\) to … the stale Atom feed\. This meant results were up to a few days old\. This was particularly annoying because my[CCBot](https://joshua.hu/ccbot-chrome-checker-bot-googlechromereleases-chromium-updates)parsed the blog’s feed to notify me \(Opera\!\) about Chromium vulnerabilities which were fixed\. When I wrote that post, the Atom feed was days behind: ``` $ date Sun Feb 23 22:33:37 AEDT 2025 $ curl --silent "https://feeds.feedburner.com/GoogleChromeReleases" | grep -o '2025-02-..' | sort -n | head -n5 2025-02-16 2025-02-13 2025-02-13 2025-02-13 2025-02-13 ``` And the RSS feed \(which historically was serving fresh results\) was redirecting to the Atom feed: ``` $ hcurl 'https://www.blogger.com/feeds/8982037438137564684/posts/default' HTTP/2 302 location: http://feeds.feedburner.com/GoogleChromeReleases ``` Well, lo and behold, a few days ago I came to discover that the RSS feed could still be accessed, if you added a secret parameter,`?redirect=false`: ``` $ hcurl 'https://www.blogger.com/feeds/8982037438137564684/posts/default?redirect=false' HTTP/2 200 cross-origin-resource-policy: cross-origin server: blogger-renderd x-content-type-options: nosniff x-xss-protection: 0 x-frame-options: SAMEORIGIN date: Sat, 21 Nov 2026 22:20:58 GMT expires: Sat, 21 Nov 2026 22:20:59 GMT cache-control: public, must-revalidate, proxy-revalidate, max-age=1 last-modified: Sat, 21 Nov 2026 14:45:03 GMT content-type: application/atom+xml; charset=UTF-8 age: 0 alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000 accept-ranges: none vary: Accept-Encoding ``` Since we can now pull in fresh results from the Chrome Releases blog, it means that CCBot can start working properly again\. Its source is still[on GitHub](https://github.com/MegaManSec/CCBot), and I’m sure Opera still uses it \(lol\)\. ## Caching with If\-Modified\-Since In terms of the[feed caching problem](https://joshua.hu/google-feedburner-broken-caching-if-modified-since)I also previously wrote about, where the Feedburner Atom feed refused any caching techniques which RSS feeds typically allow to be utilized, it turns out the`redirect=false`feed supports them\. Sort of\. Feedburner itself hasn’t changed at all\. It still doesn’t send an`ETag`, it still ignores`If\-Modified\-Since`, and it still tells everybody not to cache anything: ``` $ hcurl -H 'if-modified-since: Mon, 20 Jan 2035 10:39:12 GMT' 'https://feeds.feedburner.com/GoogleChromeReleases' HTTP/2 200 content-type: text/xml; charset=utf-8 feedburnerv2: last-modified: Sat, 21 Nov 2026 15:27:08 GMT cache-control: no-cache, no-store, max-age=0, must-revalidate pragma: no-cache expires: Mon, 01 Jan 1990 00:00:00 GMT date: Sat, 21 Nov 2026 22:35:16 GMT ``` It’s also still serving outdated results\. For example, on the 30th of October, a post published at 07:58 PT was still missing from the Feedburner feed nearly two hours later\. The`redirect=false`feed, on the other hand, does respond with`304 Not Modified`\. Sometimes\. Because of course it’s inconsistent\. The same request, with an`If\-Modified\-Since`in the future, made twelve times in a row: ``` $ URL='https://www.blogger.com/feeds/8982037438137564684/posts/default?redirect=false' $ for i in $(seq 12); do hcurl -H 'if-modified-since: Mon, 20 Jan 2035 10:39:12 GMT' "$URL" | tr -d '\r' | grep -iE '^(http|date|age)' | paste -sd ' ' -; done HTTP/2 200 date: Sat, 21 Nov 2026 22:35:17 GMT HTTP/2 200 date: Sat, 21 Nov 2026 22:35:18 GMT HTTP/2 304 date: Sat, 21 Nov 2026 22:35:18 GMT age: 0 HTTP/2 304 date: Sat, 21 Nov 2026 22:35:18 GMT age: 0 HTTP/2 304 date: Sat, 21 Nov 2026 22:35:18 GMT age: 0 HTTP/2 200 date: Sat, 21 Nov 2026 22:35:19 GMT HTTP/2 304 date: Sat, 21 Nov 2026 22:35:19 GMT age: 0 HTTP/2 304 date: Sat, 21 Nov 2026 22:35:19 GMT age: 0 HTTP/2 200 date: Sat, 21 Nov 2026 22:35:20 GMT HTTP/2 200 date: Sat, 21 Nov 2026 22:35:21 GMT HTTP/2 304 date: Sat, 21 Nov 2026 22:35:21 GMT age: 0 HTTP/2 304 date: Sat, 21 Nov 2026 22:35:21 GMT age: 0 ``` Looking at the`date`and`age`headers, we see the first request in each second gets a full`200`, and every request after it in that same second gets a`304`with an`age: 0`header\. `age`is the header a cache adds when it answers with its own stored copy instead of asking the server behind it\. The feed is served with`cache\-control: public, must\-revalidate, proxy\-revalidate, max\-age=1`, so whatever sits in front of Blogger’s`blogger\-renderd`server \(presumably some Google frontend\) is allowed to keep a copy for one second\. While that copy is fresh, the cache handles the`If\-Modified\-Since`itself, correctly, and replies with a`304`\. Once it has expired, the request goes through to`blogger\-renderd`, which ignores`If\-Modified\-Since`completely and sends back the whole feed\. Adding a cache\-busting parameter to the URL makes every request miss the cache, and then it’s a`200`every single time: ``` $ for i in $(seq 10); do curl -s -o /dev/null -w '%{http_code} ' -H 'if-modified-since: Mon, 20 Jan 2035 10:39:12 GMT' "$URL&nocache=$RANDOM"; done; echo 200 200 200 200 200 200 200 200 200 200 ``` So for anything that polls the feed every few minutes, the one\-second copy will always have expired by the time the next request comes in, and`If\-Modified\-Since`never gets a`304`\. ## Caching with If\-None\-Match What’s also interesting is that`If\-None\-Match`*does*work on the`redirect=false`feed\. The catch is that you get an`ETag`if and only if you ask for a compressed response \(wtf\)\. Without`Accept\-Encoding: gzip`, there’s no`ETag`at all: ``` $ hcurl "$URL" HTTP/2 200 server: blogger-renderd cache-control: public, must-revalidate, proxy-revalidate, max-age=1 last-modified: Sat, 21 Nov 2026 22:21:34 GMT content-type: application/atom+xml; charset=UTF-8 vary: Accept-Encoding ``` And with it: ``` $ hcurl --compressed "$URL" HTTP/2 200 content-encoding: gzip server: blogger-renderd content-length: 57817 cache-control: public, must-revalidate, proxy-revalidate, max-age=1 last-modified: Sat, 21 Nov 2026 22:21:34 GMT etag: W/"19973aaeb10ce867051869871443ee4e1f782e6a97a91bff8e8b5422e5f7f357" content-type: application/atom+xml; charset=UTF-8 vary: Accept-Encoding ``` Asking for only`br`or`zstd`doesn’t help, because the server doesn’t support them, so it sends the feed uncompressed, without an`ETag`\. Once you have the`ETag`, sending it back in`If\-None\-Match`gets a`304`every time, even with the cache\-busting parameter \(so these all come from`blogger\-renderd`itself\), and with or without`\-\-compressed`: ``` $ for i in $(seq 10); do curl -s --compressed -o /dev/null -w '%{http_code} ' -H 'if-none-match: W/"19973aaeb10ce867051869871443ee4e1f782e6a97a91bff8e8b5422e5f7f357"' "$URL&nocache=$RANDOM"; done; echo 304 304 304 304 304 304 304 304 304 304 ``` This saves quite a bit, which I had originally intended and wanted to do\. The full feed is 1,725,860 bytes uncompressed and 57,817 bytes gzipped, and a`304`is practically nothing\. Feedburner still sends 55,792 gzipped bytes \(1,615,960 uncompressed\) every time\. ## Where the redirect came from All of this is different to what I found in my original post\. Back then, the blogger\.com URL was still served by the old GData API \(that’s what the`sunset`and`link`headers in that post were about\), and it answered`If\-Modified\-Since`with a`304`\. Those headers are gone now, and the responses come from`server: blogger\-renderd`\(see the`redirect=false`response at the start of this post\), which is the same server that handles the blog’s own feeds on chromereleases\.googleblog\.com\. That’s probably also the real reason for the redirect in my last post\. The documentation I quoted in my original post said that the old GData feed URLs would keep working, but that “the response is the same as blogspot\.com feeds”\. The Chrome Releases blog’s own feeds were already redirecting to Feedburner at the time \(that’s Blogger’s “Post feed redirect URL” setting\), so once the GData API was finally switched off, the blogger\.com URL started redirecting too\. So it probably wasn’t me emailing Feedburner’s support after all, too bad\. `redirect=false`is how you get around that setting, and it’s not quite as undocumented as I originally thought: a[Feedburner help page about Google Webmaster Tools](https://support.google.com/feedburner/answer/97090)mentions`http://mybloggerblog\.blogspot\.com/feeds/posts/default?redirect=false`as a feed URL format that “should always work” for Blogger users\. Oh, and the “RSS feed” I’ve been talking about in these posts is actually an Atom feed \(`content\-type: application/atom\+xml`\), and the real RSS version is accessed with`?alt=rss&redirect=false`, which behaves exactly the same way on both blogger\.com and chromereleases\.googleblog\.com\. ## Redirecting to plain HTTP Another interesting thing is that every one of the blog’s feed URLs redirects to`http://feeds\.feedburner\.com/GoogleChromeReleases`, with`http`, not`https`, even when the feed itself was requested over https: ``` $ hcurl 'https://chromereleases.googleblog.com/feeds/posts/default' HTTP/2 302 server: blogger-renderd location: http://feeds.feedburner.com/GoogleChromeReleases ``` That means a feed reader that starts off on`https://chromereleases\.googleblog\.com/feeds/posts/default`gets downgraded to plain HTTP when it follows the redirect, and instead of sending it back to https, Feedburner just serves the whole feed over plain HTTP: ``` $ hcurl 'http://feeds.feedburner.com/GoogleChromeReleases' HTTP/1.1 200 OK Content-Type: text/xml; charset=utf-8 ``` In other words, anything subscribed to one of the Chrome Releases blog’s own feed links gets Chrome’s security release announcements unencrypted, and anybody on the network path can change them, like adding a fake release post, or removing a real security update so something like CCBot never sees it\. ## Which feed URL to use So, to sum it all up: So, if you’re polling a Blogger feed that’s redirected to Feedburner, use`?redirect=false`, ask for gzip, keep the`ETag`, and send it back as`If\-None\-Match`\. Python’s`requests`\(as used by CCBot\) already asks for gzip by default, so it’s only the last two you need to do yourself\. In other news, CCBot 1\.1\.2 has been published\!

Similar Articles

A modern feed reader (2024)

Lobsters Hottest

The author examines the decline of RSS feeds due to scraping and interference, arguing that modern feed readers must integrate alternative syndication methods to remain relevant.

Some (mostly historical) issues with the Unix load average

Lobsters Hottest

The article details the blog author's measures to block old browsers to reduce load from malicious crawlers, likely for LLM training, and addresses specific issues with feed readers like Inoreader and Feedly, as well as browsers like Vivaldi and archive services.

RSS Feed Best Practices (2022)

Hacker News Top

Kevin Cox's article lays out technical best practices for publishing blog RSS/Atom feeds, covering format choice (preferring Atom over RSS 2), correct Content-Type headers, absolute URLs, feed discovery metadata, and other compatibility tips for readers and search engines.

Serious editors are a commitment (at least for me)

Lobsters Hottest

The article discusses the challenges of blocking old browser user-agents to reduce crawler load and provides specific notes for feed readers and archival services affected by these measures.