Return allowed CORS headers in the letter case they were submitted in and update the test #29682
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #16208
This PR updates the CORS test checking that if
quarkus.http.cors.headers
property matches the headers provided in the CORS request then a correct list of headers will be returned.Additionally, a minor update to the CORS filter was made to ensure the letter case is preserved, example, if the browser sends
Access-Control-Request-Headers: x_custom
and Quarkus approves it using its case-insensitive headers match, then it should get backAccess-Control-Allowed-Headers: x_custom
, notAccess-Control-Allowed-Headers: X_CUSTOM
, the same withcontent-type
vsCONTENT-TYPE
as either the browser or Quarkus can have a lower-case or upper-case header value provided/configured