-
Bug
-
Resolution: Done
-
Blocker
-
3.1.4.Final, 3.6.3.Final
-
None
-
None
The page should display the text "hello"
Instead: The server returns an invalid signed exchange response with Chrome leading to the following message: ERR_INVALID_SIGNED_EXCHANGE. This happens in Windows.
Tomcat 9 console reads:
"Signed exchange response without "X-Content-Type-Options: nosniff" header is not supported.
Wrong magic string"
The problem doesn't show up in Firefox or Edge.
Chromium devs believe it's not a Chrome bug, and that Chrome is functioning correctly in this case.
- clones
-
RESTEASY-2198 ERR_INVALID_SIGNED_EXCHANGE localhost Chrome
- Resolved
- is incorporated by
-
JBEAP-25293 (8.0.z) RESTEasy StringTextStar provider can produce not-valid output
- Closed
- relates to
-
RESTEASY-2232 When choosing return media type, don't ignore MessageBodyWriters without @Produces annotation
- Resolved
-
JBEAP-16592 (7.4.z) RESTEasy StringTextStar provider can produce not-valid output
- Closed
-
RESTEASY-2235 When choosing return media type, don't ignore MessageBodyWriters without @Produces annotation
- Open