Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unexpected Alias translation behaviour

Status
Not open for further replies.

Hieronymous

IS-IT--Management
Aug 8, 2001
1
NL
The unexpected behaviour I see is this:-
[1] Alias /a/ "/dir1/dir2/dir3/"
[2] Alias /a/b/ "/dir1/dir2/dir3/dir4/"
[3] Alias /a/c/ "/dir1/dirX/dirY/"

If I have all three of these in the config file then only [1]and[2] will work and [3] will fail because Apache translates the /a/c/ not to the expected "/dir1/dirX/dirY/", but instead to "/dir1/dir2/dir3/c/" giving a file not found error.
Theres nothing wrong with [3] as it works OK if [1] is removed or commented out.

i.e. instead of translating the /a/c/ fakename it has taken the translation of /a/, the first Alias, and just appended 'c/' which is kind of pointless as far as I can see. The dir structure must reflect the structure of the 'Alias fakenames'. What?

I'm translating a whole website to Apache so I need to keep the existing 'Alias fakenames' pointing to the existing destinations. It doesn't seem possible with this behaviour. What I would like to know is:-

a. is this expected behaviour or do I have a problem;
have I set something up wrongly
b. if it is expected, then how do I get Apache to translate "/a/c/" correctly.

Even 'RewriteRule' doesn't seem to get round this.
Anybody any idea what has gone wrong here?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top