Atom format results not conforming to the standard

[SpriteOvO]

Routes

NOROUTE

Full routes

NOROUTE

Related documentation

https://docs.rsshub.app/guide/parameters#output-formats

What is expected?

Routes with ?format=atom parameter should output <content type="text/html" src="https://example.com/~">

What is actually happening?

Routes with ?format=atom parameter is outputting <content type="html" src="https://example.com/~">

Deployment information

RSSHub demo (https://rsshub.app)

Deployment information (for self-hosted)

No response

Additional info

This is not about route, but rather the ?format=atom parameter. According to Atom's standard RFC 4287 4.1.3.2. section:

4.1.3.2. The "src" Attribute

atom:content MAY have a "src" attribute, whose value MUST be an IRI
reference [RFC3987]. If the "src" attribute is present, atom:content
MUST be empty. Atom Processors MAY use the IRI to retrieve the
content and MAY choose to ignore remote content or to present it in a
different manner than local content.

If the "src" attribute is present, the "type" attribute SHOULD be
provided and MUST be a MIME media type [MIMEREG], rather than "text",
"html", or "xhtml". The value is advisory; that is to say, when the
corresponding URI (mapped from an IRI, if necessary) is dereferenced,
if the server providing that content also provides a media type, the
server-provided media type is authoritative.

Currently, RSSHub's Atom outputs do not conform to the standard, causing downstream parsers (such as Rust's feed-rs) to reject them.

This is not a duplicated issue

• I have searched existing issues to ensure this bug has not already been reported

[dosubot]

Hi @SpriteOvO! I'm Dosu and I’m helping the RSSHub team.

The Atom output from RSSHub currently uses <content type="html" src="...">, which violates RFC 4287 because the type attribute must be a MIME media type like text/html when src is present. This causes strict parsers (like feed-rs) to reject the feed.

This behavior comes from the code in lib/views/atom.tsx, where the <content> element is rendered with type="html" instead of type="text/html" when src is set. To fix this immediately in your own deployment, change the relevant line in lib/views/atom.tsx from:

<content type="html" src={item.link}>

to

<content type="text/html" src={item.link}>

There is an open pull request to make the Atom output spec-compliant and address this issue, along with other Atom compliance improvements (like removing RSS-specific elements and ensuring the updated field uses RFC-3339 format) see PR #20723. No configuration workaround exists; tracking that PR is the best way to follow official progress.

For now, a manual patch is the only way to ensure strict Atom compatibility.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}