-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
RESTEasy Reactive: Content type incorrect for Qute templates #25932
Milestone
Comments
FroMage
added
kind/bug
Something isn't working
area/qute
The template engine
area/rest
labels
Jun 2, 2022
/cc @geoand, @mkouba, @stuartwdouglas |
Seems like you have a fix really 😎. Mind providing a PR? |
Also, it would be great to have a simple way to reproduce this |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Jun 3, 2022
gsmet
added a commit
that referenced
this issue
Jun 9, 2022
Set content-type for Qute templates in RESTEasy Reactive
FroMage
added a commit
to FroMage/quarkus
that referenced
this issue
Jun 10, 2022
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Jun 13, 2022
(cherry picked from commit 7b56d91)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
efecf5e introduced a bug because the
TemplateResponseFilter
used to set the Content Type:While the new behaviour in
TemplateResponseUniHandler
does not:As a result, Qute HTML templates now get their content type set to
text/plain; charset=utf8
which is incorrect. A bit scary that we don't have a test for this too…The text was updated successfully, but these errors were encountered: