Changing Accept Header in PreMatching filter isn't considered by MessageBodyWriter #40019
Comments
|
Thanks for reporting. #40022 fixes the issue |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Apr 11, 2024
gastaldi
added a commit
that referenced
this issue
Apr 11, 2024
Take MediaType set in pre-match filter into account during serialization
|
Wow that was quick, thank you! Can this fix also be backported to 3.8 LTS? |
|
🙏. We do plan to backport the fix to 3.8 during the next patch release |
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Apr 17, 2024
Fixes: quarkusio#40019 (cherry picked from commit 4f86368)
zZHorizonZz
pushed a commit
to zZHorizonZz/quarkus-grpc-transcode
that referenced
this issue
Apr 24, 2024
poldinik
pushed a commit
to poldinik/quarkus
that referenced
this issue
Apr 29, 2024
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
May 15, 2024
Fixes: quarkusio#40019 (cherry picked from commit 4f86368)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
#38130 fixed just the routing, but not the rendering by MessageBodyWriters
Expected behavior
Accept Header set in the pre-matching request filter shall decide which MessageBodyWriter will be selected.
Actual behavior
Setting the Accept Header inside the pre-matching request filter doesn't affect which MessageBodyWriter is being selected.
How to Reproduce?
Output of
uname -aorverNo response
Output of
java -versionjava 17.0.9 2023-10-17 LTS
Quarkus version or git rev
3.9.3
Build tool (ie. output of
mvnw --versionorgradlew --version)Apache Maven 3.9.6
Additional information
No response
The text was updated successfully, but these errors were encountered: