HTTP/2 custom status codes
mdounin at mdounin.ru
Wed Aug 9 17:22:57 UTC 2017
On Wed, Aug 09, 2017 at 09:56:26PM +0530, Sharan J wrote:
> Thanks for the response.
> > ... [error] ... upstream sent no valid HTTP/1.0 header while reading
> response header from upstream ...
> This is logged in the error log for both HTTP/1.1 and HTTP/2. May I know
> why everything returned by the backend is considered as the response body
> in HTTP/2 alone? and not in HTTP/1.1?
It is considered to be the response body in both cases. Though in
case of HTTP/1.x nginx downgrades client's connection to HTTP/0.9
as well, and returns the HTTP/0.9 response as it was got from the
More information about the nginx