Re: proxy_next_upstream exemption for 429 "too many requests"

nt as the server responded. The 429s in this case > contain json bodies. Actually, after re-reading your email, I'm confused... 429 responses aren't matched by "proxy_next_upstream error" (with or without my patches), and are passed as-is to the client. Maybe you're using

Re: proxy_next_upstream exemption for 429 "too many requests"

Hey Marques, coincidentally, I sent patches for 429 yesterday: http://mailman.nginx.org/pipermail/nginx-devel/2016-October/009003.html http://mailman.nginx.org/pipermail/nginx-devel/2016-October/009004.html Best regards, Piotr Sikora On Wed, Oct 19, 2016 at 1:39 PM, Marques Johansson wrote

Re: [ANNOUNCE] ngx_brotli

hat breaks ngx_pagespeed. Basically, right now, ngx_pagespeed runs after Brotli compression, so it sees compressed content, which it doesn't know how to optimize... This should be fixed shortly ;) Best regards, Piotr Sikora ___ nginx mailing list

Re: [ANNOUNCE] ngx_brotli

ned by presence of "Accept-Encoding: br"), and gzip will be used for clients not supporting Brotli, but supporting gzip. Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: [ANNOUNCE] ngx_brotli

ll being actively worked on, so this will only get better over time ;) Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

[ANNOUNCE] ngx_brotli

itHub: https://github.com/google/ngx_brotli Brotli content encoding is already supported by Firefox 44 (Nightly) and it's expected to be supported by Chrome soon. Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.o

Re: nginx_slowfs_cache

solete, but it's not actively maintained either... I'll take a look later this week and fix it. But as others already suggested, don't try to beat OS with cache in RAM. The original use-case for this module was local cache for files served from NFS s

[ANNOUNCE] ngx_cache_purge-2.3

Version 2.3 is now available at: http://labs.frickle.com/nginx_ngx_cache_purge/ GitHub repository is available at: https://github.com/FRiCKLE/ngx_cache_purge/ Changes: 2014-12-23VERSION 2.3 * Fix compatibility with nginx-1.7.9+. Best regards, Piotr Sikora

[ANNOUNCE] ngx_cache_purge-2.2

Studio). Reported by Jussi Sallinen. Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Support for 3rd party zlib libraries

lib (like ours), not IPP zlib. Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Nginx + LibreSSL - a first test

hanging What Happens > # Define OPENSSL_VERSION_NUMBER 0x10002002L It should be the version they forked from (i.e. 0x1000107fL). Multiple people have complained about the OPENSSL_VERSION_NUMBER change, so hopefully they'll change it back... If not, then we can always apply the patch I provided.

Re: Nginx + LibreSSL - a first test

t, because I'm still trying to convince them that LibreSSL should present itself as OpenSSL-1.0.1, in which case no changes to nginx would be necessary. Best regards, Piotr Sikora nginx__libressl.patch Description: Binary data ___ nginx mailing list n

Re: SSL session cache lifetime vs session ticket lifetime

Hey, > Maybe SSL_CTX_set_timeout() should be moved to the beginning of > ngx_ssl_session_cache() then. http://hg.nginx.org/nginx/rev/767aa37f12de Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/m

Re: [alert] 12928#0: worker process 3958 exited on signal 11

Hey, assuming this is your whole config, could you either uncomment the access_log directive or add "access_log off"? I'm pretty sure you're hitting the bug introduced in 1.7.0: http://mailman.nginx.org/pipermail/nginx-devel/2014-June/005430.html Best r

Re: ngx_cache_purge + query string

query strings, you should use: proxy_cache_purge one backend$1$is_args$args; or alternatively, use "same location" configuration. Please refer to the documentation for details. Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org ht

Re: ngx_cache_purge + query string

config, so no one can tell. Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: It's believed that SPDY is a huge DDoS vector by itself

to is called "Network-Friendly HTTP Upgrade": http://tools.ietf.org/html/draft-tarreau-httpbis-network-friendly-00 But HTTPbis chose SPDY as a base for HTTP/2.0, so there is no point in adding support for all the proposed alternatives (even if they a

Re: Hg checkout missing config and friends

Hey, > $ ./config > -bash: ./config: No such file or directory ./auto/configure Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Any rough ETA on SPDY/3 & push?

0] https://groups.google.com/d/msg/spdy-dev/XDudMZSq3e4/oqklqhoouAsJ [1] https://bugzilla.mozilla.org/show_bug.cgi?id=912550 [2] https://code.google.com/p/chromium/issues/detail?id=318651 Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Various debugging info not shown (

Hi, > Any ideas? Your client is using TLS Session Tickets (client-side caching), so nginx-side cache isn't used for that sessions. Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: "A" Grade SSL/TLS with Nginx and StartSSL

. > I appreciate the feedback, but no need to be rude about it ;) Actually, I was trying hard to not sound rude (apparently I failed), but the fact is that calling it "A grade" and "state of the art" configuration results in people that don't know any better picking up y

Re: "A" Grade SSL/TLS with Nginx and StartSSL

e alternative, - CAMELLIA cipher suites (if you're using AES-NI), because they're too slow compared to the alternative. Overall, that's far from the state-of-the-art SSL configuration for nginx. The only good thing about it is that it's using OCSP and achieves

Re: Backend responding with 100 Continue results in the actual response being lost

on my TODO list. I just pointed it to rstarkov, because it seems that he could use working patch right now. Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Backend responding with 100 Continue results in the actual response being lost

Hello, I've made a patch for this issue a while ago: http://mailman.nginx.org/pipermail/nginx-devel/2012-December/003152.html Best regards, Piotr Sikora ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: 404s logged in error.log?

uation correctly in my configuration. Worth > double-checking. The default behavior is to log such events. You can change it with the "log_not_found" directive: http://nginx.org/r/log_not_found Best regards, Piotr Sikora ___ nginx mailing list nginx

[ANNOUNCE] ngx_cache_purge-2.1

, even if cache isn't configured. Previously, it would pass such requests to the upstream. Best regards, Piotr Sikora < piotr.sik...@frickle.com > ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Cache keeps growing despite Max_size limit

Hey Jan, Any update on the module in the near future that might fix this issue? Latest release shouldn't have this problem: http://labs.frickle.com/files/ngx_slowfs_cache-1.10.tar.gz Best regards, Piotr Sikora < piotr.sik...@fri

[ANNOUNCE] ngx_slowfs_cache-1.10

to outgrow specified "max_size" value. Best regards, Piotr Sikora < piotr.sik...@frickle.com > ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Cache keeps growing despite Max_size limit

Hey, As a quick test you may try switching to a proxy + proxy_cache setup instead of slowfs_cache to see if slowfs_cache module problem or something more general. It's a known issue with my ngx_slowfs_cache module. Best regards, Piotr Sikora < piotr.sik...@fri