Mock RSS endpoint returning HTTP 200

Live demo endpoint

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

Call it with curl

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

Call it with fetch

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

What HTTP 200 OK means

When you see it

The request succeeded and the body holds the result. This is the normal case for GET and most POST calls.

What a client should do

Read the body and move on. Do not treat a 200 with an empty body as an error unless your contract says so.

Retry?

No

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