Describe the problem and steps to reproduce it:
In-browser feed readers can't load the feed due to CORS misconfiguration. Some may be able to if they leverage WebRequest API to modify received headers, but for a resource that is inherently meant to be shared I believe it should be CORS unlocked
What happened?
Trying to load https://addons.mozilla.org/blog/feed.xml results with Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://addons.mozilla.org/blog/feed.xml. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200
What did you expect to happen?
The feed to be properly loaded
┆Issue is synchronized with this Jira Task
Describe the problem and steps to reproduce it:
In-browser feed readers can't load the feed due to CORS misconfiguration. Some may be able to if they leverage WebRequest API to modify received headers, but for a resource that is inherently meant to be shared I believe it should be CORS unlocked
What happened?
Trying to load
https://addons.mozilla.org/blog/feed.xmlresults withCross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://addons.mozilla.org/blog/feed.xml. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200What did you expect to happen?
The feed to be properly loaded
┆Issue is synchronized with this Jira Task