Skip to content

Set "Access-Control-Allow-Headers" for /share endpoint. #2

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

Merged
merged 1 commit into from
Jan 9, 2015

Conversation

dmitshur
Copy link
Member

@dmitshur dmitshur commented Jan 9, 2015

From empirical testing, this allows the /share endpoint to work in Safari on OS X, as well as in Safari and Chrome browsers on iOS.

From empirical testing, this allows the /share endpoint to work in
Safari on OS X, as well as in Safari and Chrome browsers on iOS.
@dmitshur
Copy link
Member Author

dmitshur commented Jan 9, 2015

It's possible that altering the XHR request coming in from the frontend to not include Content-Type may be an alternative way to get /share endpoint to work without this change.

But I'm not sure if that's better or worse. Setting Content-Type seems like a good idea.

@dominikh
Copy link
Member

dominikh commented Jan 9, 2015

LGTM

dmitshur added a commit that referenced this pull request Jan 9, 2015
Set "Access-Control-Allow-Headers" for /share endpoint.
@dmitshur dmitshur merged commit 4021407 into master Jan 9, 2015
@dmitshur dmitshur deleted the set-more-cors-headers branch January 9, 2015 07:05
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

Successfully merging this pull request may close these issues.

2 participants