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

Lack of CORS headers (access-control-allow-origin) should force a space into cache mode #94

Open
eastein opened this issue Nov 23, 2013 · 2 comments

Comments

@eastein
Copy link

eastein commented Nov 23, 2013

https://github.com/SpaceApi/validation-plugins/blob/master/headers-hosting-consideration.php is the warnings code as is

see issue #36 for history background.

We need to have some way of dealing with the fact that lack of CORS header makes it totally unusable for a js web application to try to hit the spaces directly. As much as we would rather everyone fixed their end point, it would be nice to fix the issue from the API central point. We could make it be in 10 minute cache or even an hour, so as to penalize the spaces for failing to comply.

@slopjong
Copy link

Here's the list with spaces that don't respect the acao header: http://pastebin.com/raw.php?i=7DtVuFgN

@brimstone
Copy link

I think that apps should be able to function without the directory, keeping the spaceapi as distributed as possible.
I think that proper CORS headers should be required for 0.14.
I think it would be nice to continue to cache the endpoints as we currently do, and provide a ?cached=true option of some sort to the directory for apps that don't required live data or are OK with a third party caching the endpoints.

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

3 participants