[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Virtual Hosting and 2.0 browsers
- Subject: Re: [cobalt-users] Virtual Hosting and 2.0 browsers
- From: "Pierre Chopot" <pierre.chopot@xxxxxxxxxxx>
- Date: Mon May 22 09:51:56 2000
Hello
Taken from the Apache Documentation: (http://www.apache.org/docs/vhosts/name-based.html)
=============================
Compatibility with Older Browsers
As mentioned earlier, there are still some clients in use who do not send the required data for the
name-based virtual hosts to work properly. These clients will always be sent the pages from the first
virtual host listed for that IP address (the primary name-based virtual host).
There is a possible workaround with the ServerPath directive, albeit a slightly cumbersome one:
Example configuration:
NameVirtualHost 111.22.33.44
<VirtualHost 111.22.33.44>
ServerName www.domain.tld
ServerPath /domain
DocumentRoot /web/domain
</VirtualHost>
What does this mean? It means that a request for any URI beginning with "/domain" will be served from
the virtual host www.domain.tld This means that the pages can be accessed as
http://www.domain.tld/domain/ for all clients, although clients sending a Host: header can also access it
as http://www.domain.tld/.
In order to make this work, put a link on your primary virtual host's page to
http://www.domain.tld/domain/ Then, in the virtual host's pages, be sure to use either purely relative
links (e.g., "file.html" or "../icons/image.gif" or links containing the prefacing /domain/ (e.g.,
"http://www.domain.tld/domain/misc/file.html" or "/domain/misc/file.html").
This requires a bit of discipline, but adherence to these guidelines will, for the most part, ensure that your
pages will work with all browsers, new and old.
=============================
*********** BEGIN REPLY SEPARATOR ***********
On 22/05/2000 at 10:10 Brian Curtis wrote:
>Hmm, and his reason for not updating to a newer browser is? Just curious.
>
>The problem is that old browsers do not support the HTTP/1.1 spec and Name
>Based virtual hosting (many sites on one IP). The only easy solution would
>be to assign different IPs to the necessary VirtualHosts. Other options
>include creating a script of some sort which captures the requested domain,
>and processing the request based on that information.
>
>BC
>
>
>----- Original Message -----
>From: "Ervin Kosch" <ervkosch@xxxxxxxxxxxx>
>Sent: Monday, May 22, 2000 9:31 AM
>Subject: [cobalt-users] Virtual Hosting and 2.0 browsers
>
>
>> This is probably an old question but I have a client who is using, wait
>for
>> the shook, IE 2.0 and Mosaic. It seems that when they issue a request to
>a
>> server they only get my default page and can't access any of my virtual
>> hosts. Is there a way around it?
>>
>
>
>
>_______________________________________________
>cobalt-users mailing list
>cobalt-users@xxxxxxxxxxxxxxx
>To Subscribe or Unsubscribe, please go to:
>http://list.cobalt.com/mailman/listinfo/cobalt-users
*********** END REPLY SEPARATOR ***********
Pierre Chopot
Zapilou 0476568866
pierre.chopot@xxxxxxxxxxx