Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(rss): use "application/rss+xml" as default content type and allow… #12643

Closed
wants to merge 1 commit into from

Conversation

kunyan
Copy link
Contributor

@kunyan kunyan commented Dec 5, 2024

… set custom charset

According to https://www.rssboard.org/rss-mime-type-application.txt The MIME type for RSS feed should be "application/rss+xml" It also need to set the charset in content type for non-english content

Changes

  • Set the content type "application/rss+xml"
  • Allow user use different charset in content type, utf-8 is default

Testing

Docs

Copy link

changeset-bot bot commented Dec 5, 2024

🦋 Changeset detected

Latest commit: 2d9820c

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@kunyan kunyan force-pushed the fix/rss-encoding branch 2 times, most recently from 32753ea to 82947f8 Compare December 5, 2024 11:26
… set custom charset

According to https://www.rssboard.org/rss-mime-type-application.txt
The MIME type for RSS feed should be "application/rss+xml"
It also need to set the charset in content type for non-english content
@ascorbic
Copy link
Contributor

ascorbic commented Dec 5, 2024

Thanks. Changing the mimetype makes sense, but I'm unsure about the charset change. The encoding is already set to UTF-8 in the XML declaration. Is there a reason that the user might want to change that? If there is, we'd need to ensure that the generated feed also used that encoding and had the correct encoding in the declaration.

@kunyan
Copy link
Contributor Author

kunyan commented Dec 5, 2024

Looks the entire project are using utf-8. so I'll send another PR for this changes without charset option

#12644

@kunyan kunyan closed this Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants