Welcome! Log In Create A New Profile

Advanced

Re: HTTP/2 custom status codes

Maxim Dounin
August 09, 2017 01:24PM
Hello!

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
backend.

--
Maxim Dounin
http://nginx.org/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

HTTP/2 custom status codes

Sharan J August 09, 2017 11:18AM

Re: HTTP/2 custom status codes

Maxim Dounin August 09, 2017 11:38AM

Re: HTTP/2 custom status codes

Sharan J August 09, 2017 12:28PM

Re: HTTP/2 custom status codes

Maxim Dounin August 09, 2017 01:24PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 198
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready