-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Add Access-Control-Allow-Credentials for CORS settings #2182
Labels
Comments
|
+1, is there a fix for this anywhere? |
I needed that as well and now have an experimental version working for me. |
ha, I also have a rough and ready version too. need to polish it a lot, so you might beat me to it. Will be good to compare approaches |
6 tasks
Ready for review |
asprouse
added a commit
to asprouse/serverless
that referenced
this issue
Nov 17, 2016
7 tasks
asprouse
added a commit
to asprouse/serverless
that referenced
this issue
Dec 5, 2016
asprouse
added a commit
to asprouse/serverless
that referenced
this issue
Jan 18, 2017
eahefnawy
added a commit
that referenced
this issue
Jan 26, 2017
Added Access-Control-Allow-Credentials for CORS settings fixes #2182
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a Feature Proposal
Description
Right now I am developing a cross origin resource sharing (CORS) application which requires sharing cookies. The server is required to return the Access-Control-Allow-Credentials header set to true to allow this. While there is way to set headers, methods and origins with serverless, there is no easy way of setting the allow-credentials header. Will have to go to aws console to enable this which is a headache for maintenance.
Similar or dependent issues:
Additional Data
The text was updated successfully, but these errors were encountered: