Quarkus REST - Be more forgiving when adding headers #47546
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gsmet
changed the title
This comment has been minimized.
This comment has been minimized.
|
Thanks for taking care of this! Can a test be added easily that reproduces the original problem? |
geoand
approved these changes
Jun 18, 2025
The JAX-RS API is very loose and allows adding Object and in some cases we actually add a List to the headers and we need to take this into account. While I'm usually not for handling things this way, the API is not enforcing things properly so I think we really need to handle this ourself. Fixes quarkusio#47507
This comment has been minimized.
This comment has been minimized.
Status for workflow
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The JAX-RS API is very loose and allows adding Object and in some cases we actually add a List to the headers and we need to take this into account.
While I'm usually not for handling things this way, the API is not enforcing things properly so I think we really need to handle this ourself and be more forgiving if a list is added.