$request_method variable shows wrong value

I have a setup where I'm using an Accel-Redirect header in php like this: header("X-Accel-Redirect: /testxxx.php?".$_SERVER['QUERY_STRING']); Furthermore I'm using HTTP/2.0 and SSL, running on nginx 1.11.8. The problem is: When doing a POST request on my upload.php (which then does an x-accel-red

Are there plans for Nginx supporting HTTP/2 server push?

Is there something like a release timeline for HTTP/2 server push feature in Nginx? It would help make https connections faster and get rid of one TCP roundtrip. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,269749,269749#msg-269749 ___ ngi

Re: Multi Certificate Support with OCSP not working right

Hello Maxim, Thank you! Good news: The patch seems to work. br, Can Posted at Nginx Forum: https://forum.nginx.org/read.php?2,269371,269433#msg-269433 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Multi Certificate Support with OCSP not working right

Hello, When using 2 certificates, 1 RSA (using AlphaSSL) and 1 ECDSA (using Lets Encrypt), and I try to connect via RSA SSL connection, nginx throws this error: "OCSP response not successful (6: unauthorized) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org" So it is u

Re: Multi certificate support returns Letsencrypt Intermediate Certificate twice

Thanks a lot for the fast response! Posted at Nginx Forum: https://forum.nginx.org/read.php?2,267240,267249#msg-267249 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Multi certificate support returns Letsencrypt Intermediate Certificate twice

Hello folks, I have the following setup: Nginx 1.11.0 Libressl 2.3.4 1 Letsencrypt RSA 2048 certificate 1 Letsencrypt ECDSA p256 certificate The certificate files are both chained. Both have the Letsencrypt RSA 2048 X3 intermediate certificate at the end of the file. The problem is: Nginx retur

Re: proper setup for forward secrecy

This topic is 3 years old by now. Has something changed on OpenSSL key generation since then? Does anybody know? Posted at Nginx Forum: http://forum.nginx.org/read.php?2,229538,257690#msg-257690 ___ nginx mailing list nginx@nginx.org http://mailman.ng

Re: [calling all patch XPerts !] [PATCH] RSA+DSA+ECC bundles

It would be great if the official nginx had support for multiple certificates. Some bigger sites are already deploying ECDSA certificates. To be able to support older clients while using ECDSA we need multi certificate support. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,253440,2576

Re: Fastcgi_cache sometimes returns statuscode 500

I've had 2 cases with status code 500 now since setting error log to debug level: The error msg: "epoll_wait() reported that client prematurely closed connection while sending request to upstream" It's interesting to note that: If a "normal" file (no caching involved) is requested and the client

Re: Fastcgi_cache sometimes returns statuscode 500

Maxim Dounin Wrote: > This makes me think that it is just a cached 500 response from > your backend then. If in doubt, you can obtain details using > debug log, see http://wiki.nginx.org/Debugging. > I also considered that, but then I'd need to have at least hundreds of 500 status codes since

Re: Fastcgi_cache sometimes returns statuscode 500

Maxim Dounin Wrote: --- > Hello! > > Try looking into the error log. When nginx returns 500, it used to > complain to the error log explaining the reason. > Unfortunately the error log for that vhost does not reveal anything at the specific t

Fastcgi_cache sometimes returns statuscode 500

hm/ngxcache levels=1:2 use_temp_path=off keys_zone=MYSITE:5M max_size=50M inactive=2h; Maybe somebody knows advice? br, mastercan Posted at Nginx Forum: http://forum.nginx.org/read.php?2,256977,256977#msg-256977 ___ nginx mailing list

Re: RE: Building nginx with TCP_FASTOPEN enabled

Lukas Tribus Wrote: > > Don't upgrade libc because of this (it will mess your system up). > > Just define it manually when compiling nginx by passing it to the > compiler: > -DTCP_FASTOPEN=23 > > Thank you! This seems to define the constant. I simply added --with-cc-opt="-DTCP_FASTOPEN=23" to

Re: RE: Building nginx with TCP_FASTOPEN enabled

Lukas Tribus Wrote: > Don't upgrade libc because of this (it will mess your system up). > > Just define it manually when compiling nginx by passing it to the > compiler: > -DTCP_FASTOPEN=23 > Which command accepts the -D flag? Where exactly do I set this option? Thanks in advance Posted at Ngi

Re: Building nginx with TCP_FASTOPEN enabled

Maxim Dounin Wrote: > > Try looking into objs/autoconf.err, it has details about configure > test failures. Most likely, the TCP_FASTOPEN constant isn't > defined since your glibc isn't recent enough, something like 2.18+ > is needed. > Yes, you're right. glibc was the problem. I tried to bu

Building nginx with TCP_FASTOPEN enabled

Hello, I've tried to use "fastopen" in the listen directive but nginx gave me an error that the option is unkown. I'm using nginx 1.7.4 on Debian Wheezy 3.14.13 kernel. I've compiled nginx myself. When I run the configure command, I get: "checking for TCP_FASTOPEN ... not found" 'cat /proc/sys/

Re: SSL_STAPLING when network is unreachable

Maxim Dounin Wrote: > It's to configure timeout used by nginx's own nonblocking resolver > (http://nginx.org/r/resolver) - that is, for name resolution done > by running nginx. To configure system resolver you should > use your system's settings, usually /etc/resolv.conf. > > (Actually, sole p

Re: SSL_STAPLING when network is unreachable

Hello Maxim, > On startup, nginx does name resolution of various names in a > configuration files, using system resolver. This includes initial > resolution of OCSP responders if stapling is used. If your system > resolver doesn't have internet access and blocks trying to resolve > names - s

SSL_STAPLING when network is unreachable

Hello, I've encountered a problem with nginx 1.5.10. I'm running nginx on a highly available system (2 cluster node). When node1 fails, node2 is automatically coming into play. A few days ago the internet connection was bad - on both nodes. They could ping the gateway only sporadically. Node2 bec