Received: (qmail 27843 invoked by uid 2012); 18 Jun 1999 14:22:32 -0000
Message-Id: <19990618142232.27842.qmail@hyperreal.org>
Date: 18 Jun 1999 14:22:32 -0000
From: Anthony Ryan <news@bradford.ac.uk>
Reply-To: news@bradford.ac.uk
To: apbugs@hyperreal.org
Subject: behaviour/style of .htaccess files has changed with "require user xxx"
X-Send-Pr-Version: 3.2

>Number:         4606
>Category:       mod_access
>Synopsis:       behaviour/style of .htaccess files has changed with "require user xxx"
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Jun 18 07:30:00 PDT 1999
>Last-Modified:
>Originator:     news@bradford.ac.uk
>Organization:
apache
>Release:        1.3.6
>Environment:
Solaris 5.5.1 sun4u sparc, SUNW,Ultra-1
Apache 1.3.6
>Description:
With Apache1.2.5 we created .htaccess files with a separate line for each require user statement e.g

<Files index.html>
require user bob
require user ben
require user dan
</Files>

With Apache1.3.6 only the first user is allowed access; the other lines are ignored.
>How-To-Repeat:

>Fix:
We can workaround by putting all the users on one line of course (as specified in the new documentation):

require user bob ben dan

But is it possible to make the old style .htaccess files work properly ?
In this small example it doesn't matter but we have many users who have created
large .htaccess files with lots of usernames in.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]