We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When a browser makes a CORS requests with credentials set to include, Resgate should include in the response the header:
credentials
include
Access-Control-Allow-Credentials: true
If the header is not included, the browsers will not expose the response to frontend JavaScript code.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials
headerAuth
The text was updated successfully, but these errors were encountered:
GH-181: Added Access-Control-Allow-Credentials header in response to …
f27b6bb
…HTTP requests
GH-181: Added tests for headerAuth and Access-Control-Allow-Credentia…
08366df
…ls header
Merge pull request #182 from resgateio/bugfix/gh-181-access-control-a…
7cd3202
…llow-credentials-header Bugfix/gh 181 access control allow credentials header
Resolved in #182
Sorry, something went wrong.
jirenius
No branches or pull requests
Issue
When a browser makes a CORS requests with
credentials
set toinclude
, Resgate should include in the response the header:If the header is not included, the browsers will not expose the response to frontend JavaScript code.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials
Notes
headerAuth
.The text was updated successfully, but these errors were encountered: