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-redirect to testxxx.php) the $request_method has the value "GET". I have a sby mastercan - Nginx Mailing List - English
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.by mastercan - Nginx Mailing List - English
Hello Maxim, Thank you! Good news: The patch seems to work. br, Canby mastercan - Nginx Mailing List - English
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 using the wrong responder. Following build (custom compiled): Nginx 1.11.3 Openssby mastercan - Nginx Mailing List - English
Thanks a lot for the fast response!by mastercan - Nginx Mailing List - English
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 returns this intermediate certificate twice when connecting via https. Regardless whether youby mastercan - Nginx Mailing List - English
This topic is 3 years old by now. Has something changed on OpenSSL key generation since then? Does anybody know?by mastercan - Nginx Mailing List - English
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.by mastercan - Nginx Mailing List - English
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 closes the connection prematurely, the status code is 200 and the response bby mastercan - Nginx Mailing List - English
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 other users are hitting the same page some seconds before or later. They get statusby mastercan - Nginx Mailing List - English
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 times in question...by mastercan - Nginx Mailing List - English
Hello, Nginx (all versions since September 2014, but at least 1.7.9, 1.7.10) sometimes returns HTTP status code 500, when serving pages from fastcgi_cache. Each time this happens, following conditions hold true: *) $upstream_cache_status = HIT (so we don't even hit php-fpm) *) $body_bytes_sent = 0 (which is strange, because I've got an error page defined for http code 500, that is obviouslby mastercan - Nginx Mailing List - English
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 my configure command. I think this will work (I'm cby mastercan - Nginx Mailing List - English
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 advanceby mastercan - Nginx Mailing List - English
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 build an nginx deb package on a development machine with updated glibc libs aby mastercan - Nginx Mailing List - English
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/net/ipv4/tcp_fastopen' gives me "3" - I also tried it with thby mastercan - Nginx Mailing List - English
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 purpose of nginx's own resolver is to be able to > resolve names when ngiby mastercan - Nginx Mailing List - English
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 - so nginx will do. I see. But what is the parameter "resolver_timeout"by mastercan - Nginx Mailing List - English
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 became the active one and tried to start nginx. Nginx did not even come up. I replayed the wholby mastercan - Nginx Mailing List - English
Igor Sysoev Wrote: ------------------------------------------------------- > On Wed, Oct 21, 2009 at 07:44:38AM -0400, > mastercan wrote: > > > Maxim Dounin Wrote: > > > -------------------------------------------------- > ----- > > > - error_page 404 @fallback; > > > + error_page 404 = @fallback; > > > > >by mastercan - Nginx Mailing List - English
Maxim Dounin Wrote: ------------------------------------------------------- > - error_page 404 @fallback; > + error_page 404 = @fallback; > I guess this option with the = sign was added in one of the latest development versions? I'm using 0.7.62 (stable), where this is not recognized. If it's "safe" to switch to the development version, I could try thby mastercan - Nginx Mailing List - English
Maybe I should add, that the returned HTML is *always* correct, whether memcached finds it in memory or not...it's only the status code header that is wrong.by mastercan - Nginx Mailing List - English
Hi, I have the following config (just a snippet): set $memcached_key $uri; default_type "text/html; charset=utf-8"; error_page 404 @fallback; The problem is, that whenever memcached does not find the value in memory, I get a 404 status code. My fallback is an Apache HTTP server which handles the request via mod_php. In case of a 404 the request is forwarded to Aby mastercan - Nginx Mailing List - English