You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When making a (big) post request to a Quarkus endpoint, the response contains duplicate Transfer-Encoding: chunked headers. This is not valid per the HTTP specification and can cause issues with clients or proxies that strictly validate responses. In my case it clashes with caddy proxy (caddy is using a very strict go lib). I saw this in Quarkus Version 3.26.2 and 3.23.4
Expected behavior
The response should include the Transfer-Encoding: chunked header only once.
Actual behavior
HTTP/1.1 200 OK
Transfer-Encoding: chunked
Content-Type: application/json
Transfer-Encoding: chunked