nice RSA + ECDSA certs support !
what's the recommended way to setup HTTP Public Key Pinning with regards to
dual SSL certificates ?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267113,267124#msg-267124
___
nginx mailing list
nginx@nginx.
Hello Nginx users,
Now available: Nginx 1.11.0 for Windows
https://kevinworthington.com/nginxwin1110 (32-bit and 64-bit versions)
These versions are to support legacy users who are already using Cygwin
based builds of Nginx. Officially supported native Windows binaries are at
nginx.org.
Announce
Hello!
On Tue, May 24, 2016 at 01:15:54PM -0400, hheiko wrote:
> We are runnging nginx reverse proxy on windows, the upstream consists of two
> lunixes based Apache/PHP Backend Servers. There is only one PHP application
> to be proxied. After starting nginx everything works fine, but then the
> b
We are runnging nginx reverse proxy on windows, the upstream consists of two
lunixes based Apache/PHP Backend Servers. There is only one PHP application
to be proxied. After starting nginx everything works fine, but then the
backends become partly unresponsive and nginx is logging
2016/05/24 18:42
On Tue, May 24, 2016 at 10:17:55AM -0400, hbajaj2 wrote:
Hi there,
> I need to use proxy_pass directive for the upstream server which has
> query_string, which allows it to authenticate to the upstream server. How
> can i ensure that query string is pass-on with every request that goes via
> this
Changes with nginx 1.11.024 May 2016
*) Feature: the "transparent" parameter of the "proxy_bind",
"fastcgi_bind", "memcached_bind", "scgi_bind", and "uwsgi_bind"
directives.
*) Feature: the $request_id variable.
*) Feature: the "m
I need to use proxy_pass directive for the upstream server which has
query_string, which allows it to authenticate to the upstream server. How
can i ensure that query string is pass-on with every request that goes via
this reverse proxy.
My simplified configuration is
location /RetrieveProductWS
On 24/05/16 13:21, Francis Daly wrote:
On Tue, May 24, 2016 at 11:10:31AM +0100, Andrew Hutchings wrote:
Hi there,
As if by magic:
http://nginx.org/en/docs/http/ngx_http_core_module.html#chunked_transfer_encoding
Will that work here?
That directive seems to be about nginx sending a respo
Francis Daly Wrote:
---
> On Tue, May 24, 2016 at 11:10:31AM +0100, Andrew Hutchings wrote:
>
> Hi there,
>
> > As if by magic:
> http://nginx.org/en/docs/http/ngx_http_core_module.html#chunked_transf
> er_encoding
>
> Will that work here?
>
>
On Tue, May 24, 2016 at 11:10:31AM +0100, Andrew Hutchings wrote:
Hi there,
> As if by magic:
> http://nginx.org/en/docs/http/ngx_http_core_module.html#chunked_transfer_encoding
Will that work here?
That directive seems to be about nginx sending a response to a client,
and choosing not to send
Hey Andrew,
Thanks for your reply. Actually we tried that already and still faced the
same issue. It can easily be reproduced; send any GET request with header
"transfer-encoding: chunked".
We tried the below already.
chunked_transfer_encoding off;
proxy_buffering off;
Posted at Nginx Forum:
As if by magic:
http://nginx.org/en/docs/http/ngx_http_core_module.html#chunked_transfer_encoding
Kind Regards
Andrew
On 23/05/16 21:21, bclod wrote:
We have a client sending a GET request who is also erroneously sending a
transfer-encoding : chunked Header.
This is causing nginx to wait for
12 matches
Mail list logo
