Re: How to send proxy cache status to backend server?

Thanks, It is working. I was checking wrong variable name. I have noticed that when catch is being "REVALIDATED", backend receives "EXPIRED" and upstream receives "REVALIDATED". Is this correct ? On Mon, Mar 17, 2014 at 8:20 AM, Maxim Dounin wrote: > Hello! > > On Sat, Mar 15, 2014 at 01:14:51

[ANN] Windows nginx 1.5.12.2 Cheshire

20:29 18-3-2014 nginx 1.5.12.2 Cheshire Based on nginx 1.5.12 (release 18-3-2014) with; + nginx security advisory (CVE-2014-0133) + echo-nginx-module v0.51 (upgraded 18-3-2014) + Nginx-limit-traffic-rate-module (https://github.com/bigplum/Nginx-limit-traffic-rate-module) + lua-nginx-module v0.9.6

Re: starting

Hello, On Tue, Mar 18, 2014 at 8:18 PM, Haris Bogdanovich wrote: > How to get started with nginx ? > ​First of all, welcome to nginx community :o)​ ​All the basic principles can be found there:​ ​http://nginx.org/en/docs/beginners_guide.html ​ > Is there some tutorial for Lisp usets ? > What'

starting

Hi. How to get started with nginx ? Is there some tutorial for Lisp usets ? What's the connection between nginx and hunchentoot ? Why do I get something about nginx when trying to access hunchentoot mailing list ? Thanks___ nginx mailing list nginx@ngi

Re: Converting Rewrites to Nginx

Ugh, I spoke too soon. It works when the urls are like this: http://example.com/install?step=1 But it does not work when the urls are like this: http://example.com/dashboard/ http://example.com/profile/ Sometime it brings back 404 Not Found and other times it comes back with 500 Internal Error

回复： Why doesn't Nginx rewrite directive support '@' named_location?

Hi, > Simple answer is: > > Because rewrite directive is to rewrite request URI as per it's name, > while redirecting a request to a named location preserves request > URI (and that's the sole purpose of named locations). > > More complex one is: > > Support of named locations in rewrites was

nginx security advisory (CVE-2014-0133)

Hello! A bug in the experimental SPDY implementation in nginx was found, which might allow an attacker to cause a heap memory buffer overflow in a worker process by using a specially crafted request, potentially resulting in arbitrary code execution (CVE-2014-0133). The problem affects nginx 1.3.

nginx-1.4.7

Changes with nginx 1.4.7 18 Mar 2014 *) Security: a heap memory buffer overflow might occur in a worker process while handling a specially crafted request by ngx_http_spdy_module, potentially resulting in arbitrary code execution (CV

nginx-1.5.12

Changes with nginx 1.5.1218 Mar 2014 *) Security: a heap memory buffer overflow might occur in a worker process while handling a specially crafted request by ngx_http_spdy_module, potentially resulting in arbitrary code execution (CV

Re: SSL session cache lifetime vs session ticket lifetime

Hello! On Tue, Mar 18, 2014 at 03:42:33PM +0400, kyprizel wrote: > What will be the best way to do it? Probably a flag in ngx_slab_pool_t will be good enough. > > > On Tue, Mar 18, 2014 at 3:33 PM, Maxim Dounin wrote: > > > Hello! > > > > On Tue, Mar 18, 2014 at 03:26:10PM +0400, kyprizel w

Re: Why doesn't Nginx rewrite directive support '@' named_location?

On Tuesday 18 March 2014 22:52:06 yzprofile wrote: > Hi, > > I have a simple question: > > Why doesn't Nginx rewrite directive support '@' named_location? > > : ) The "rewrite" directive is intended to change request URI, while the named locations are intended for redirecting without URI chan

Re: Why doesn't Nginx rewrite directive support '@' named_location?

Hello! On Tue, Mar 18, 2014 at 10:52:06PM +0800, yzprofile wrote: > Hi, > > I have a simple question: > > Why doesn't Nginx rewrite directive support '@' named_location? Simple answer is: Because rewrite directive is to rewrite request URI as per it's name, while redirecting a request to a

Re: Converting Rewrites to Nginx

Thanks for pointing me in the right direction. That last part gave me a redirect loop error, so I changed it to this: rewrite ^/(.*)$ /index.php?url=$1; I applied it, loaded the site, restarted nginx, and loaded the site again. It seems to work. Hopefully, my change is not just a fluke but will c

Why doesn't Nginx rewrite directive support '@' named_location?

Hi, I have a simple question: Why doesn't Nginx rewrite directive support '@' named_location? : ) Thanks ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: PHP type. Thread Safe or Non Thread Safe?

Felix Quintana Wrote: --- > What kind of php to use as a fastcgi in nginx on Windows? NTS. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,248447,248454#msg-248454 ___ nginx mailing list ngi

Re: Converting Rewrites to Nginx

location / { try_files $uri $uri/ /index.php?url=$1 last; } Maybe what you want here is: location / { try_files $uri $uri/ @rewrite; } location @rewrite { rewrite ^/(.*)$ /index.php/$1; } On Tue, Mar 18, 2014 at 12:05 PM, parkerj wrote: > I have been trying to convert the follow

Re: PHP type. Thread Safe or Non Thread Safe?

This ML is intended for nginx-related problems. Yours is PHP-related. Either ask this question on some PHP ML or RTFM ... With regards, --- *B. R.* ___ nginx mailing list nginx@n

PHP type. Thread Safe or Non Thread Safe?

What kind of php to use as a fastcgi in nginx on Windows? ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Converting Rewrites to Nginx

I have been trying to convert the following htaccess rules to nginx with no luck. RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-l RewriteRule ^(.+)$ index.php?url=$1 [QSA,L] I've tried: location / { if (!-e $request_filename){ rew

Re: SSL session cache lifetime vs session ticket lifetime

What will be the best way to do it? On Tue, Mar 18, 2014 at 3:33 PM, Maxim Dounin wrote: > Hello! > > On Tue, Mar 18, 2014 at 03:26:10PM +0400, kyprizel wrote: > > > Hi, > > currently SSL session lifetime and SSL ticket lifetime are equal in > nginx. > > > > If we use session tickets with big e

Re: SSL session cache lifetime vs session ticket lifetime

Hello! On Tue, Mar 18, 2014 at 03:26:10PM +0400, kyprizel wrote: > Hi, > currently SSL session lifetime and SSL ticket lifetime are equal in nginx. > > If we use session tickets with big enough lifetime (12hrs), we get a lot of > error log messages while allocating new sessions in shared memory:

SSL session cache lifetime vs session ticket lifetime

Hi, currently SSL session lifetime and SSL ticket lifetime are equal in nginx. If we use session tickets with big enough lifetime (12hrs), we get a lot of error log messages while allocating new sessions in shared memory: 2014/03/18 13:36:08 [crit] 18730#0: ngx_slab_alloc() failed: no memory in S