31 messages in ru.sysoev.nginxRe: error_page and named locations
FromSent OnAttachments
cynixDec 10, 2008 6:32 am 
cynixDec 10, 2008 7:51 am 
Igor SysoevDec 10, 2008 8:11 am.fastcgi
Almir KaricDec 10, 2008 8:28 am 
Igor SysoevDec 10, 2008 8:49 am 
cynixDec 11, 2008 2:09 am 
Igor SysoevDec 11, 2008 2:51 am 
Igor SysoevDec 11, 2008 3:09 am 
Phillip B OldhamDec 11, 2008 3:47 am 
Igor SysoevDec 11, 2008 4:31 am 
cynixDec 11, 2008 4:39 am 
Jean-Philippe MoalDec 11, 2008 5:55 am 
Jim OhlsteinDec 11, 2008 6:07 am 
Igor SysoevDec 11, 2008 6:18 am 
Igor SysoevDec 11, 2008 8:09 am 
Ezra ZygmuntowiczDec 11, 2008 8:34 am 
mikeDec 11, 2008 10:51 am 
Igor SysoevDec 11, 2008 11:55 am 
Jean-Philippe MoalDec 11, 2008 12:44 pm 
mikeDec 11, 2008 2:18 pm 
Igor SysoevDec 12, 2008 12:13 am 
mikeDec 12, 2008 12:54 am 
Igor ClarkDec 12, 2008 1:49 am 
Igor SysoevDec 12, 2008 3:12 am 
Igor ClarkDec 12, 2008 7:05 am 
Igor SysoevDec 12, 2008 7:31 am 
Mark AlanDec 12, 2008 8:22 am 
Ezra ZygmuntowiczDec 12, 2008 9:00 am 
KT WalrusDec 12, 2008 2:01 pm 
Igor ClarkDec 12, 2008 2:06 pm 
MerlinJan 2, 2009 11:08 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: error_page and named locationsActions...
From:Igor Clark (lis@ruby-forum.com)
Date:Dec 12, 2008 7:05:11 am
List:ru.sysoev.nginx

Igor Sysoev wrote:

On Fri, Dec 12, 2008 at 10:50:21AM +0100, Igor Clark wrote:

If there's an implied

3) falls back to a named location if no file is found

then I think it would be good to have some reference to the fallback functionality, even if it's optional, as explicit names are more clear, and for people trying to read documentation, directive names with 'hidden' functionality are hard to find.

Yes, however, fallback is not optional. The directive has at least two parameters: the last one will be always fallback and it may be @named_location or /uri/that/should/not/fail.

Ah, OK.

The 'uri' bit, on the other hand, can be assumed, as we know from the fact that we're in a location block that this directive is dealing with a particular URI, so we need to express what this directive does to fulfil the request for that URI.

So I'd like to suggest something like 'try_files_with_fallback' - it's perhaps a bit wordy, but seems to express more clearly what's happening.

I think fallback should not be mentioned.

Yes, I think you're right, because it's one of a list of options being tried, and in a sense it's not actually a fallback, it's just the last option.

use_* is good because it makes it clear that one of the options /will/ be used; try_* is good because it makes it clear that the arguments are tried in turn until one /can/ be used. *_file is perhaps less good because it implies only files can be used in the list.

Maybe use_resource or try_resource? I'd probably go for use_resource, otherwise, out of the existing proposed names, I'd vote for use_file.