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
Using http filter config is disabling CORS options #38155
Comments
In any page, or some specific one? |
any page |
I tried with Chrome and it only worked on localhost:8080 whether the filter was active or nor |
cc @sberyozkin |
@geoand did you reproduce? |
this is a nasty bug |
Yeah, I'll have a fix soon |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Jan 15, 2024
The previous behavior would completely replace existing response headers Fixes: quarkusio#38155
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Jan 15, 2024
The previous behavior would completely replace existing response headers Fixes: quarkusio#38155
geoand
added a commit
that referenced
this issue
Jan 15, 2024
Make sure `quarkus.http.filter` headers don't remove existing headers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using a filter, it doesn't add the CORS headers anymore.
Expected behavior
The cors headers (or any header that is set up elsewhere) should be added in addition to the other headers
Actual behavior
The cors headers are removed
How to Reproduce?
Clone this and start https://github.com/ia3andy/reproducer-cors with
quarkus dev
Use this in you browser console (on a tab with a different domain opened):
It fails with CORS error.
Remove the filter from the properties and it works.
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
3.5+
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: