Return-Path: Delivered-To: apache-bugdb-archive@hyperreal.org Received: (qmail 8584 invoked by uid 6000); 9 Nov 1997 09:44:49 -0000 Received: (qmail 8572 invoked by uid 2012); 9 Nov 1997 09:44:47 -0000 Date: 9 Nov 1997 09:44:47 -0000 Message-ID: <19971109094447.8571.qmail@hyperreal.org> To: apache-bugdb@apache.org, dgaudet@apache.org, sommers@sfo.com From: dgaudet@hyperreal.org Subject: Re: general/704: VirtualHost relative paths are being over-ridden by global Alias paths Sender: apache-bugdb-owner@apache.org Precedence: bulk Synopsis: VirtualHost relative paths are being over-ridden by global Alias paths State-Changed-From-To: feedback-closed State-Changed-By: dgaudet State-Changed-When: Sun Nov 9 01:44:47 PST 1997 State-Changed-Why: Sorry I took so long to close this one out. Apache is behaving correctly. is a relative URL which the client translates into an absolute URL before sending the request to the server. Suppose this tag is embedded in a page at http://www.vhost.com/index.html. In that case, the relative "images/foo.gif" is mapped to the absolute "http://www.vhost.com/images/foo.gif". This results in the URI "/images/foo.gif", which is properly Aliased by your global Alias directive. i.e. in this case and refer to the exact same object. Regarding your other example, in ~userdir situations, the relative URL "images/foo.gif" refers to the absolute URI "/~userdir/images/foo.gif" which is definately different than "/images/foo.gif". Your only options are to not use "images" URIs in vhosts, or to remove the global Alias /images. Dean