httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 49927] New: Explanation of the #limit directive
Date Tue, 14 Sep 2010 13:41:53 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=49927

           Summary: Explanation of the #limit directive
           Product: Apache httpd-2
           Version: 2.3-HEAD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Documentation
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: olivier.pons@gmail.com


Here :

http://httpd.apache.org/docs/2.0/mod/core.html#limit


Someone wrote:


The purpose of the <Limit>  directive is to restrict the effect of the access
controls to the nominated HTTP methods. For all other methods, the access
restrictions that are enclosed in the <Limit> bracket will have no effect. The
following example applies the access control only to the methods POST, PUT, and
DELETE, leaving all other methods unprotected:

Shouldn't it be:

"leaving all other methods untouched"

?
(i.e. if there already are some protections on GET there will be untouched)

?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message