Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
AH03467: h2_task: unable to parse status line #138
I have a setup where the apache http2 server is acting as a reverse proxy using mod_proxy
I regularily see these errors in the apache log (one every 5 mins or so).
From what I can gather looking at the mod_http2 code, it seems that mod_http2 thinks that is parsing a serialized http/1.1 response but instead has html, gzipped data, a png file, or basically something that is not an http/1.1 response.
Could this be a state error in mod_http2?
It looks like a similar problem was reported in issue #133 however I am not using mod_proxy_http2.
Interesting. Will have a closer check, but this looks like mod_http2 expects an interim response, like 100, but it there is still some data pending from a previous request. Hmm.
It must be the same issue as #133. Interesting. Do you know more about the requests that trigger this? Can you give me an example on how mod_proxy is configured (no hostname or addresses, pls.)?
Hmm, can it be that someone makes HEAD requests against a handler in the backend that sends the data as if it is a GET? That would leave the response body on the proxy connection. When that is re-used, mod_http2's interim response complains about it.
As it looks, the request will fail and mod_proxy will try it on a new connection. If that is true, the ERROR logging is too high level and DEBUG should be enough.
Can we check if the backend implements HEAD requests correctly?
Thanks for the quick response Stefan. I'll try to respond to the questions you asked above:
Do you know more about the requests that trigger this?
Can you give me an example on how mod_proxy is configured (no hostname or addresses, pls.)?
Also, are these messages all from different task ids? h2_task(nn-xx)?