The following reply was made to PR mod_alias/1856; it has been noted by GNATS.

From: Randy Jae Weinstein <[EMAIL PROTECTED]>
To: Dean Gaudet <[EMAIL PROTECTED]>
Cc: Lars Eilebrecht <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: mod_alias/1856: Alias directive allowable in htaccess
Date: Sun, 22 Feb 1998 20:14:20 -0500 (EST)

 Aaaaah, your first paragraph will explain my dilema.  Case closed.  Thanks
 for the info and sorry for the inconvenience.
 
 > No it won't read the destination's parent directories.  It does read the
 > destination's .htaccess however.  There's a note somewhere in the docs
 > explaining that when apache does traverse a symlink it *does not* rewrite
 > the filename -- so if /foo/bar is a symlink to /do/wah/ditty, and a
 > reference to /foo/bar/blah is made, then apache looks for rules covering
 > /foo/bar/blah, NOT /do/wah/ditty/blah.
 > 
 > Using 1.2.6 or 1.3b6-dev (which should be the same as all the released
 > versions in this respect) I was not able to verify your bug.  For example,
 > I did this:
 > 
 > cd ap/htdocs
 > ln -s ~/public_html dg
 > cd dg
 > echo "Header add testing this" > .htaccess
 > 
 > start httpd
 > 
 > % telnet localhost 8080
 > Trying 127.0.0.1...
 > Connected to localhost.
 > Escape character is '^]'.
 > HEAD /dg/ HTTP/1.0
 > 
 > HTTP/1.1 200 OK
 > Date: Mon, 23 Feb 1998 01:01:46 GMT
 > Server: Apache/1.3b6-dev
 > testing: this
 > Connection: close
 > Content-Type: text/html
 > 
 > Connection closed by foreign host.
 > 
 > note the "testing: this" header.  The .htaccess file of the destination
 > was read and processed.
 > 
 > Dean
 > 
 > On Sun, 22 Feb 1998, Randy Jae Weinstein wrote:
 > 
 > > I submitted the bug due to the fact that I have already created a Symbolic
 > > Link (ln -s), on my system, and the server already has AllowOverride All
 > > set, and yet it doesn't read the correct htaccess files!  It only reads of
 > > the SOURCE of where the link is, and not the destintatino and the
 > > destination's parent directories!  Maybe the status should be changed to a
 > > bug fix instead of a request?  As I have already tried what Dean said and
 > > it has not worked.
 > > 
 > > > (grrr... the bugdb-script doesn't send a copy to a
 > > >  changed originator address.)
 > > > 
 > > > >  [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. ]
 > > > >  
 > > > >  
 > > > >  Synopsis: Alias directive allowable in htaccess
 > > > >  
 > > > >  Comment-Added-By: [EMAIL PROTECTED]
 > > > >  Comment-Added-When: Sun Feb 22 16:38:51 PST 1998
 > > > >  Comment-Added:
 > > > >  (corrected bogus return address by using address from
 > > > >   PR#1855)
 > > > >  
 > > > >  To repeat Dean's previous comment: .htaccess files
 > > > >  are read in the destination of a symlink (unless
 > > > >  disabled via AllowOverride).
 > > > >  
 > > > >  Originator-Changed-From-To: [EMAIL PROTECTED]
 > > > >  Originator-Changed-By: [EMAIL PROTECTED]
 > > > >  Originator-Changed-When: Sun Feb 22 16:38:51 PST 1998
 > > > 
 > > > 
 > > 
 > >                                                    Cheers,
 > >  =|  __  __    T    |                              Randy Jae
 > >  =| | .\/. |   O  M |
 > >   *--\ \/ /--* O  A |                                  Lehigh University
 > >   |  / __ \    T  N |  Randy Jae Weinstein         NYU College of 
 > > Dentistry!
 > >   | |_|  |_|   H    |  [EMAIL PROTECTED]                  D.D.S. 2B!!
 > > --==>> http://Pages.NYU.EDU/~rw263/
 > > 
 > > 
 > 
 > 
 
                                                    Cheers,
  =|  __  __    T    |                              Randy Jae
  =| | .\/. |   O  M |
   *--\ \/ /--* O  A |                                  Lehigh University
   |  / __ \    T  N |  Randy Jae Weinstein         NYU College of Dentistry!
   | |_|  |_|   H    |  [EMAIL PROTECTED]                  D.D.S. 2B!!
 --==>> http://Pages.NYU.EDU/~rw263/
 

Reply via email to