Mock RSS endpoint returning HTTP 502

Live demo endpoint

Any method, any path. Returns 502 Bad Gateway with Content-Type: application/rss+xml. OPTIONS returns 204 with CORS headers.

Call it with curl

curl -i https://demo-rss-502.supercrontab.com/

Call it with fetch

const res = await fetch("https://demo-rss-502.supercrontab.com/");
console.log(res.status); // 502
const body = await res.text();

What HTTP 502 Bad Gateway means

When you see it

A proxy or load balancer got an invalid response from the upstream app, often during a deploy or a crash.

What a client should do

Retry with exponential backoff. Deploys usually finish within a minute, so a few retries are enough.

Retry?

Yes, with backoff

Sample response body

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Mock feed</title>
    <link>https://supercrontab.com/mock/rss</link>
    <description>One item, always the same</description>
    <item>
      <title>Item 42</title>
      <link>https://supercrontab.com/mock/rss/200</link>
      <guid>42</guid>
    </item>
  </channel>
</rss>

A valid RSS 2.0 feed with one item. Point a feed reader or a cron job at it to test polling.

Questions