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
Unable to decode with compressed response from origin #92
Comments
After some tests I can confirm that the go http server normalize the headers to "Fields" before send it to Vulcain. The error was that Caddy does not send a uncompress response to Vulcain when the origin server return a GZipped response, so Vulcain can't decode it and return a empty object. Should I report that to the Caddy team or is responsability of each http handler to uncompress the response? |
BrandonlinU
changed the title
Inconsistencies with headers' case-sensitive
Unable to decode with compressed response from origin
Jun 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was working in a Api Platform app with Caddy behind a IIS server. The IIS server manages HTTP/2 and stream the headers in lowercase to the Caddy server running HTTP/1.1. According to the RFC, the HTTP/2 headers should be case-senstive and with all headers in lowercase, and the HTTP/1.1 should be case-insensitive. The code that extracts the headers only verifies the "Field" header, in a case-sensitive manner, causing that the Fields header can not be readed correctly.
I would try to test a patch, but I don't know Go, so I can't guarranty nothing.
The text was updated successfully, but these errors were encountered: