>Number: 2666 >Category: general >Synopsis: Using <Limit Get> directive (access.conf) doesn't work as it >did in 1.3.0 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Jul 22 14:50:01 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.1 >Environment: Linux happy 2.0.34 #6 Tue Jul 21 11:28:48 CDT 1998 i586 unknown >Description: If you use the <Limit Get> directive in 1.3.1, it won't work until you change get to all caps (eg. <Limit GET>) in the 'access.conf' file. 1.3.0 was more tolerant to mixed cases in directives.
Nothing major, but I though people should know. >How-To-Repeat: >Fix: In the 'access.conf' file, change all of your <Limit Get> directives to <Limit GET> and everything should be fine. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
