On Tue, Apr 30, 2002 at 01:27:05AM +0200, Marcus.Zoller wrote:

> Hmm... a redirect sends the Location: http://new-url...
> header as reply and this will result in a new request from the user
> and will change the URL displayed.

Not necessarily. If you open up a frame in which the redirect takes place
you still see the old url with the contents of the new-url.

Ramin

> 
> In your case this will show http://33.44.55.66 instead of http://xyz.com
> after the redirect was sent from 11.33.44.55.66.
> 
> If this is what you were looking for, changin the DNS record is a better
> solution.
> 
> If you want to hide your two machines behind one address for multiple virtual
> domains, you can't do this with sending back a redirect to the user.
> 
> Assume xyz.com, abc.com is hosted on a NT (the 22...) box and foo.com and
> bar.com is hosted on a Linux box (33...) and you want a common DNS setup for
> all those domains. In this case all four domains have the 11... address.
> 
> If the user requests xyz.com and the apache for the 11. redirects to 22.,
> how does the NT box decide if it is xyz.com or abc.com without having
> the domain within the URL string?
> 
> Maybe I forgot or misunderstand something here but I don't know about some kind
> of HTTP redirect that will keep the request string and just let the useragent
> connect to a new address for the same url requested?
> 
> 
> -- 
> Marcus
> 

Reply via email to