Re: HTTP/2 custom status codes

2017-08-09 Thread Maxim Dounin
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 everythin

Re: HTTP/2 custom status codes

2017-08-09 Thread Sharan J
Hi, 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

Re: HTTP/2 custom status codes

2017-08-09 Thread Maxim Dounin
Hello! On Wed, Aug 09, 2017 at 08:46:41PM +0530, Sharan J wrote: > Hello, > > I am using Nginx as a reverse proxy and have enabled HTTP/2. For a > particular request, my back-end server sends a custom 4 digit status code > (say ). > > When connecting via HTTP/1.1, the exact status code is r