Re: 1.9.13 and non_idempotent

Hello! On Tue, Mar 29, 2016 at 08:04:33PM -0700, Frank Liu wrote: > It's a custom error code, think of it as if http_404, so if the first > upstream can't handle this request , it will send "404" saying it is not > for me, please try next, nginx should then send the same request to next > upstrea

Re: 1.9.13 and non_idempotent

It's a custom error code, think of it as if http_404, so if the first upstream can't handle this request , it will send "404" saying it is not for me, please try next, nginx should then send the same request to next upstream. On Tuesday, March 29, 2016, Maxim Dounin wrote: > Hello! > > On Tue,

Re: 1.9.13 and non_idempotent

Hello! On Tue, Mar 29, 2016 at 06:34:59PM -0700, Frank Liu wrote: > If I explicitly configured to retry next upstream based on a > certain http_xxx, will that stop working if a request is a POST with > 1.9.13? Yes. There is no real difference between a network error and an HTTP error returned

1.9.13 and non_idempotent

If I explicitly configured to retry next upstream based on a certain http_xxx, will that stop working if a request is a POST with 1.9.13? For other http code, I like the idea of not retry if it is non idempotent but for one http_xxx, I want retry no matter what type of request. Thanks Frank __

Re: nginx-1.9.13

Hello Nginx users, Now available: Nginx 1.9.13 for Windows https://kevinworthington.com/nginxwin1913 (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

Re: proxy_read_timeout vs proxy_next_upstream_timeout

Those directives works at very different levels. proxy_next_upstream_timeout allocates a time for nginx to find a proper upstream (configured with proxy_next_upstream

Re: packages for the dynamic modules. testing required.

Hello, We've just published the official packages for the 1.9.13 release and two more dynamic module packages were added on all supported platforms: - perl, nginx-module-perl - njs, nginx-module-njs Enjoy, On 24/02/2016 22:08, Sergey Budnevitch wrote: > Hello. > > Previously we built

nginx-1.9.13

Changes with nginx 1.9.1329 Mar 2016 *) Change: non-idempotent requests (POST, LOCK, PATCH) are no longer passed to the next server by default if a request has been sent to a backend; the "non_idempotent" parameter of the "proxy_next_upstre

Re: multiple named captures in map regex

On Mon, Mar 28, 2016 at 11:30:32PM -0400, Cole Tierney wrote: Hi there, > Is it possible to have more than one named capture in a map regex? In a map regex, yes. In a "value" part of a map, no. http://nginx.org/r/map says The resulting value can be a string or another variable > When I try t

proxy_read_timeout vs proxy_next_upstream_timeout

Hi If you set read timeout 2 min and next upstream timeout 50 seconds, will nginx break the current connection at 50 second or will it let the read finish until 2min? Thanks Frank ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/l

Re: Nginx generating different md5 sums for same key causing cache to become corrupt

Hello! On Tue, Mar 29, 2016 at 08:36:37AM -0400, pirish wrote: > Hello, > Currently we use nginx 1.8.1 on redhat 7. We have reverse proxy caching > enabled but are experiencing unexpected behaviour. Our caching key is > $scheme$request_method$host$request_uri$. On the first visit to a page,

Nginx generating different md5 sums for same key causing cache to become corrupt

Hello, Currently we use nginx 1.8.1 on redhat 7. We have reverse proxy caching enabled but are experiencing unexpected behaviour. Our caching key is $scheme$request_method$host$request_uri$. On the first visit to a page, a cache file with the correct md5 sum of the key is created. If you visi