You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(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:
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:
(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
: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, thenosniff
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) thenosniff
option was dropped. Or both.A nginx configuration for setting the mime type might look include:
The text was updated successfully, but these errors were encountered: