RE: mod_auth-any/5241: .htaccess asks for the user's password twi ce (fwd)

[Marc Slemko <ma...@znep.com>]

The following reply was made to PR mod_auth-any/5241; it has been noted by GNATS.

From: Marc Slemko <ma...@znep.com>
To: Apache bugs database <ap...@apache.org>
Cc:  Subject: RE: mod_auth-any/5241: .htaccess asks for the user's password twi
 ce (fwd)
Date: Wed, 3 Nov 1999 11:17:36 -0700 (MST)

 ---------- Forwarded message ----------
 Date: Wed, 3 Nov 1999 18:12:18 -0000 
 From: o.cook@etoncollege.org.uk
 To: marc@apache.org, apache-bugdb@apache.org
 Subject: RE: mod_auth-any/5241: .htaccess asks for the user's password twi
     ce
 
 Including a trailing "/" fixes it. Thanks
 
 Ol.
 
 ---
 "I'm a bomb squad technician. If you see me running, try to keep up" ---
 seen on the back of a bomb squadder's jacket.
 
 
 
 > -----Original Message-----
 > From: marc@apache.org [mailto:marc@apache.org]
 > Sent: 03 November 1999 18:09
 > To: apache-bugdb@apache.org; marc@apache.org; 
 > o.cook@etoncollege.org.uk
 > Subject: Re: mod_auth-any/5241: .htaccess asks for the user's password
 > twice
 > 
 > 
 > [In order for any reply to be added to the PR database, ]
 > [you need to include <ap...@Apache.Org> in the Cc line ]
 > [and leave the subject line UNCHANGED.  This is not done]
 > [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!         ]
 > 
 > 
 > Synopsis: .htaccess asks for the user's password twice
 > 
 > State-Changed-From-To: open-closed
 > State-Changed-By: marc
 > State-Changed-When: Wed Nov  3 10:09:10 PST 1999
 > State-Changed-Why:
 > You are almost certainly accessing a directory without
 > including a trailing "/", as is required.  When Apache
 > corrects it, it has to send a redirect.  If that redirect
 > uses a different host name than the one you did originally,
 > you will have to authenticate again.  Either set your
 > ServerName to the same name that is used to access the server
 > or set "UseCanonicalName off".
 >