atom feed28 messages in ru.sysoev.nginxRe: Location problems
FromSent OnAttachments
Matteo NiccoliFeb 19, 2008 1:37 am 
Denis F. LatypoffFeb 19, 2008 2:22 am 
Matteo NiccoliFeb 19, 2008 2:38 am 
Igor ClarkFeb 19, 2008 3:04 am 
Denis F. LatypoffFeb 19, 2008 3:23 am 
Igor ClarkFeb 28, 2008 11:41 am 
Igor SysoevFeb 28, 2008 12:49 pm 
Igor ClarkFeb 29, 2008 1:38 am 
Igor SysoevFeb 29, 2008 2:41 am 
Igor ClarkFeb 29, 2008 3:13 am 
Igor SysoevFeb 29, 2008 3:30 am 
Igor ClarkFeb 29, 2008 7:36 am 
Cliff WellsFeb 29, 2008 11:20 pm 
Igor SysoevFeb 29, 2008 11:47 pm 
Igor ClarkMar 3, 2008 6:07 am 
Igor SysoevMar 3, 2008 6:15 am 
Igor ClarkMar 3, 2008 8:52 am 
Igor SysoevMar 3, 2008 8:55 am 
Igor ClarkMar 3, 2008 9:43 am 
Igor SysoevMar 3, 2008 9:49 am 
Igor ClarkMar 4, 2008 6:13 am 
Igor ClarkMar 6, 2008 9:40 am 
Igor SysoevMar 8, 2008 12:05 pm 
Igor ClarkMar 10, 2008 3:04 am 
Igor SysoevMar 10, 2008 3:28 am.method
Igor ClarkMar 10, 2008 3:51 am 
Igor ClarkMar 31, 2008 11:14 am.conf, .conf, .log
Igor ClarkApr 7, 2008 3:04 am 
Subject:Re: Location problems
From:Igor Sysoev (is-G@public.gmane.org)
Date:Mar 3, 2008 6:15:23 am
List:ru.sysoev.nginx

On Mon, Mar 03, 2008 at 02:07:41PM +0000, Igor Clark wrote:

Hi Igor,

I've been trying this out taking the approach of the example you gave me - very happy about it, and have a couple of questions.

- Using "error_page 404 @fallback" instead of "if (! -f " seems to generate 404 errors in the log for every hit transferred to the @fallback. Is that inevitable?

log_not_found off;

- Is there any way to use "fastcgi_intercept_errors on" with this setup?

Yes. But you also need to add

location @fallback {

recursive_error_pages on;

to redirect it via error_page, because this is second error_page redirection in request.

Thanks very much, Igor

On 1 Mar 2008, at 07:47, Igor Sysoev wrote:

On Fri, Feb 29, 2008 at 11:20:42PM -0800, Cliff Wells wrote:

On Fri, 2008-02-29 at 14:31 +0300, Igor Sysoev wrote:

location / { error_page 404 = @fallback; }

location @fallback { fastcgi_pass ... fastcgi_param SCRIPT_FILENAME /path/to/frontend.php; fastcgi_param QUERY_STRING control_path=$uri; ... }

Igor,

I've seen you use the "@" prefix on locations in several examples you've given people. Is this just a notation you prefer or does it have some significance?

Yes, these are named locaitons, they had appeared in 0.6.6 and 0.5.31. The main feature - while internal redirect via error_page $uri is not changed, so they are handily to use in fallback handlers.

The named locaiton are always internal and do not intersect with site's URI space.

In 0.6.27 post_action will support named location too.

-- Igor Sysoev http://sysoev.ru/en/

-- Igor Clark // POKE // 10 Redchurch Street // E2 7DD // +44 (0)20 7749 5355 // www.pokelondon.com

-- Igor Sysoev http://sysoev.ru/en/