Skip to content
This repository has been archived by the owner on Dec 17, 2021. It is now read-only.

Replace JSONP with CORS #13

Closed
konklone opened this issue May 23, 2014 · 3 comments
Closed

Replace JSONP with CORS #13

konklone opened this issue May 23, 2014 · 3 comments
Milestone

Comments

@konklone
Copy link
Contributor

As recommended in WhiteHouse/api-standards#14, and by others, CORS is a far superior replacement for JSONP.

CORS is not supported on some older browsers, but unless XHR (Ajax) support in IE8 and below is a priority for the API, there are good reasons (complexity, security) to avoid adding it altogether. In other words, no JSONP without good reason, and CORS defaulting to on.

@konklone konklone added this to the v1 milestone May 23, 2014
@NoahKunin
Copy link
Contributor

I'd go even farther w/JSONP. IE 9 and below should not be supported - full stop. We do no one any favors by allowing them to use flawed browsers.

@konklone
Copy link
Contributor Author

konklone commented Jun 7, 2014

This is a good reminder that this is an expression of what we do more than saying what everyone else should do. 👍 to that, feel free to make the edit if you like.

@NoahKunin
Copy link
Contributor

IE8 if fully EOL'd, so I'll definitely make that edit at min.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants