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

Safari cannot detect Starred feed as an atom file #223

Open
gwire opened this issue Sep 10, 2017 · 1 comment
Open

Safari cannot detect Starred feed as an atom file #223

gwire opened this issue Sep 10, 2017 · 1 comment

Comments

@gwire
Copy link

gwire commented Sep 10, 2017

(This may be an issue for the specific hosted feedbin.com configuration, or the app?)

I wanted to add the feed of starred articles to the "Shared Links" feature of the Safari browser, but the browser won't recognise it as an atom file.

This is actually expected behaviour for Safari. The issue is that feedbin.com sets the following headers when requesting, e.g., https://feedbin.com/starred/example.xml:

 Content-Type: application/xml; charset=utf-8
 X-Content-Type-Options: nosniff

The registered MIME type for Atom is application/atom+xml, but it's usually enough to set it to xml and let the application work out that it's an Atom file. However, the nosniff option is explicitly telling the browser not to do this.

It would be great if either a) the content-type was specified as application/atom+xml or b) the nosniff option was dropped. Or both.

A nginx configuration for setting the mime type might look include:

location ~ /starred/.+\.xml {
  types { application/atom+xml xml; }
}
@ScottHelme
Copy link

I vote that the Content-Type should be declared correctly ;-)

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

No branches or pull requests

2 participants