Redirects and content type headers

Redirect behavior and XML content types affect feed fetch reliability.

Checked by FeedInspector

Capability checks

Metrics

Feed delivery includes HTTP details such as redirect chains, final URL, protocol, and response content type.

Long or unstable redirects add latency and may be blocked. Incorrect content type headers can cause parser rejection.

FeedInspector records redirect count, HTTPS usage, and checks tech.contentType against XML like MIME types.

Problem: Feed URL redirects through multiple hosts.
Fix: Serve the feed from one stable canonical endpoint.
Problem: Server sends text/html for feed XML.
Fix: Return application/rss+xml, application/atom+xml, or application/xml.

HTTP response example

HTTP/1.1 301 Moved Permanently
Location: https://example.com/feed.xml

HTTP/1.1 200 OK
Content-Type: application/rss+xml; charset=utf-8