-
Notifications
You must be signed in to change notification settings - Fork 976
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
fix: cors headers not added to the response #2922 #2934
fix: cors headers not added to the response #2922 #2934
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2934 +/- ##
=======================================
Coverage 76.19% 76.19%
=======================================
Files 309 309
Lines 19031 19032 +1
=======================================
+ Hits 14501 14502 +1
Misses 3405 3405
Partials 1125 1125
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Thanks! |
Hello @kstasik |
@alnr @vinckr can you guys update your docker images on dockerhub https://hub.docker.com/r/oryd/kratos/tags? thank you! |
Hey @vladyslav2 |
A release for including the CORS fix has not yet been tagged. If you require this fix right now, consider building kratos from source. Should be straightforward 👍 |
@alnr already did. |
Kratos v0.11.1 is out now 👍 |
thanks |
CORS response headers not added to the response:
Related issue(s)
#2922
Checklist
introduces a new feature.
contributing code guidelines.
vulnerability. If this pull request addresses a security vulnerability, I
confirm that I got the approval (please contact
[email protected]) from the maintainers to push
the changes.
works.
Further Comments
I just wanted to quickly fix the issue. I noticed that upgrading the docker image breaks CORS. Checked the changes before releases and reverted the cause of the problem.
BTW: I noticed that response headers are added by the middleware but they disappear somehow during the processing of the request:
Maybe someone with larger knowledge about negroni and libraries knows a better fix for this issue (order of middlewares etc.).