11 messages in ru.sysoev.nginxRe: doc: limit_except
FromSent OnAttachments
Gregg ReynoldsMar 15, 2007 11:11 am 
Igor SysoevMar 15, 2007 11:23 am 
Igor SysoevMar 15, 2007 11:29 am 
Gregg ReynoldsMar 15, 2007 1:51 pm 
Igor SysoevMar 16, 2007 12:00 am 
Gregg ReynoldsMar 16, 2007 1:59 am 
Igor SysoevMar 16, 2007 2:17 am 
Gregg ReynoldsMar 16, 2007 4:17 am 
Igor SysoevMar 16, 2007 4:26 am 
Gregg ReynoldsMar 16, 2007 7:37 am 
Igor SysoevMar 16, 2007 8:10 am 
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: doc: limit_exceptActions...
From:Igor Sysoev (is-G@public.gmane.org)
Date:Mar 15, 2007 11:23:16 am
List:ru.sysoev.nginx

On Thu, Mar 15, 2007 at 12:11:35PM -0600, Gregg Reynolds wrote:

I'm unsure of the meaning of limit_except. This is how I understand the syntax:

limit_except METHODS { (ALLOW-CLAUSE | DENY-CLAUSE)* }

where METHODS is a list of HTTP method tokens and the clauses are

('allow' | 'deny') SP+ (IPADDR | HOSTNAME | 'all' )+ ;

Is that it? Can anything else go in the block? Any other allowed values?

My understanding is that "limit_except" simply associates a method with a list of allow/deny clauses governing use of the method.

Yes. Currently several directives are allowed here only: allow/deny auth_basic_... proxy_pass and perl

What confuses me is the name. Why "except"? Is "accept" the intention? As in "server, please limit the acceptance of this method according to the allow/deny clauses that follow."

This directive is similar to http://httpd.apache.org/docs/2.2/mod/core.html#limitexcept

Currenty there may be one limit_except block per location. Sometimes I think it may be usefull to allow several limit/limit_except blocks per location to use something like this:

limit LOCK UNLOCK { perl ... }

limit_expect GET { ... }