Is there a wait to get at a module's main conf inside the loc conf's init?

2017-08-09 Thread ptcell
>From the debugger I can see that it's probably some offset into cf->ctx[index].main_conf, but I don't see anyway of knowing what that index is inside the loc create callback. Is there any other way of getting this?Getting it at loc merge time would be acceptable too. void *ngx_http_my_modul

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

post_action, rewrites, and proxy_pass

2017-08-09 Thread Michael Payne
v1.4.6 I'm attempting to proxy pass requests to AWS API Gateway, but they are not reaching the endpoint. Example of my configuration below. Requests come through as something like some.domain.com/some_resource The final post_action hop at the bottom is attempting to pass the request and its para

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

HTTP/2 custom status codes

2017-08-09 Thread Sharan J
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 returned to the client but, when connection via HTTP/2, the response headers along

Re: nginx security advisory (CVE-2017-7529)

2017-08-09 Thread Maxim Dounin
Hello! On Thu, Jul 20, 2017 at 10:32:15PM -0700, Shuxin Yang wrote: > I try to exploit this bug in an attempt to do something nasty :-). > However, the more I dig into it, the more I get confused. No comments on this, sorry. We generally avoid providing exploitation details to minimize im