one-to-many messaging

Tom Thomson ukcrypto at chiark.greenend.org.uk
Mon, 14 Apr 2008 20:36:17 +0100


Sgriobh James Firth:
>
> Tom Thomson wrote:
> > (a) the URL as typed is not transmitted, so
> > that description is not useful within the public telecommunication
> > system
>
> The URL as typed IS transmitted in most cases (HTTP/HTTPS).  It's how
> multiple sites are presented on the same IP.

No it isn't.  The Host requests-header is included in the HTTP message
to achieve that, and is NOT the same as the URL. To be precise it is a
copy of that part of the URL which lies between the @ (if an
authorization is present) or the // (if an authorization is not present)
and the first /.

If you think either that "//example.tld:888/a/b/c" (the URL) is
transmitted or that "host: example.tld:888" (what is transmitted in the
Host header) is the URl you are mistaken - the only URL that is
transmitted from the client to the server is the content-location
request header ("content-location: a/b/c" in the current example) which
no-one wants to claim is traffic data (I hope).  Unless things have
changes since I was messing about with this stuff, which is always
possible.

M.