W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2001

Re: GoLive, Host and Destination Header

From: Hartmut Warncke <hwarncke@adobe.com>
Date: Tue, 07 Aug 2001 16:50:10 +0200
Message-ID: <3B700022.682B1778@adobe.com>
To: Stefan Eissing <stefan.eissing@greenbytes.de>
CC: w3c-dist-auth@w3.org


Stefan Eissing wrote:

> I stumbled today about different behaviours when
> it comes to treatment of Host and Destination headers,
> which I'd like to get your point of view on.
> GoLive (5.0 tryout) does send a Host header in request,
> however it omittes the port part. So, if you have a server
> localhost:8080, GoLive will send a Host header "Host: localhost".
> However in Destination headers, GoLive uses the correct URLs, e.g.
> Destination: http://localhost:8080/test.html
> Now, my Servlet checks these headers on a COPY/MOVE and responds
> with a 502 (Bad Gateway), as source and destination do not match.
> I checked with mod_dav: same behaviour:
> I checked with IIS: works. IIS seems to disregard the host part
> of the destination URL and performs the MOVE/COPY.
> Now, you can look at it two ways:
> a) Well, nobody can move to a destination on a different server,
>    so ignoring the host part in Destination is Ok.
> b) Non-matching host parts is an error and should be reported as such.
> What do you think? How is your server handling this?
> //Stefan
> PS. I don't know if there is a newer version of GoLive where the
> host header is fixed. Anyone can verify or comment on that?

No, there is no newer GoLive version, GoLive 5.0 is the current version. I
will check what I can arrange with the Host header in the future,

Best, Hartmut
Received on Thursday, 9 August 2001 06:35:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:23 UTC