Received: (qmail 72429 invoked by uid 501); 18 Oct 2001 11:00:43 -0000 Message-Id: <20011018110043.72428.qmail@apache.org> Date: 18 Oct 2001 11:00:43 -0000 From: John Burnett Reply-To: johnfburnett@yahoo.com To: submit@bugz.apache.org Subject: Aliases that don't end in '/' not working X-Send-Pr-Version: 3.110 >Number: 8572 >Category: mod_alias >Synopsis: Aliases that don't end in '/' not working >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Oct 18 04:10:01 PDT 2001 >Closed-Date: >Last-Modified: Thu Oct 18 04:30:00 PDT 2001 >Originator: johnfburnett@yahoo.com >Release: 1.3.22 >Organization: apache >Environment: Win NT 4.0 Service Pack 6 >Description: Greetings, I tried hard to find this in the bug database and elsewhere, so I think it's a new bug. I'm trying to create an Alias "http://localhost/mamamia": I have a directory "C:/hello/myalias" containing an index.html file. If I enter the following entry for my alias: Alias /mamamia "C:/hello/myalias" ,restart Apache and then access URL "http://localhost/mamamia" the browser times-out after a while and I get a TCP_ERROR. If I try to access the URL "http://localhost/mamamia/" the index page is displayed successfully. Not dure if it's helpful, but if I change the Alias entry as follows: Alias /mamamia "C:/hello/myalias/" i.e add a trailing slash to the "real" directory name, restart Apache and then access the URL "http://localhost/mamamia/" again I get different behaviour - this time the directory root of C:/hello/myalias is displayed showing that it contains the file index.html (rather than displaying the CONTENTS of the index.html file as it does above). This behaviour is not consistent with that described in the documentation nor articles I read about Apache aliases. LOGS ----- no error.log access.log contains: 127.0.0.1 - - [18/Oct/2001:12:30:56 +0200] "GET /mamamia HTTP/1.1" 301 323 >How-To-Repeat: Create an alias not ending in a slash and try and access in a URL that also DOES NOT CONTAIN A SLASH. If the URL ends in a slash there is no problem. >Fix: Nope - sorry. >Release-Note: >Audit-Trail: From: John Burnett To: submit@bugz.apache.org, apache-bugdb@apache.org Cc: Subject: Re: mod_alias/8572: Aliases that don't end in '/' not working Date: Thu, 18 Oct 2001 04:28:54 -0700 (PDT) BTW I forgot to mention I added the necessary Directory directive to enable access to the myalias directory. If I use URL "http://localhost/mamamia/index.html that works fine - but I would expect that when I call URL "http://localhost/mamamia" the webserver should retrun be the index.html in the myalias directory. --- submit@bugz.apache.org wrote: > Thank you very much for your problem report. > It has the internal identification `mod_alias/8572'. > The individual assigned to look at your > report is: apache. > > >Category: mod_alias > >Responsible: apache > >Synopsis: Aliases that don't end in '/' not > working > >Arrival-Date: Thu Oct 18 04:10:01 PDT 2001 __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com >Unformatted: [In order for any reply to be added to the PR database, you need] [to include 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! ]