Mock RSS endpoint returning HTTP 422

Live demo endpoint

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

Call it with curl

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

Call it with fetch

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

What HTTP 422 Unprocessable Content means

When you see it

The request was well formed but failed validation: an email without @, a date in the past, a value out of range.

What a client should do

Show the validation errors to the user and fix the payload. Retrying the same body cannot succeed.

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