[175] in WWW Security List Archive
Re: Source-routed URLs
daemon@ATHENA.MIT.EDU (Larry Masinter)
Sat Oct 1 08:43:02 1994
To: www-security@ns1.rutgers.edu
From: Larry Masinter <masinter@parc.xerox.com>
Date: Fri, 30 Sep 1994 22:52:43 PDT
Reply-To: Larry Masinter <masinter@parc.xerox.com>
> There are two constructs. The one used by HTTP seems to be merely to
> prepend the protocol and host part of each hop's URL to the front of
> the destination URL. Each hop receives the stacked URLs and strips
> off its part of the address, passing on the remaining part of the
> URL, until a hop realizes that the destination file is local.
> An example of going through a relay to the document on a real system:
> http://relay.sys.org/http://real.sys.org/document.html
Actually, this doesn't work.
http://relay.sys.org/http://real.sys.org/document.html
is defined to mean:
open a connection to relay.sys.org, port 80
send
GET /http://real.sys.org/document.html HTTP/1.0
Accept: ...
Note the initial /. There is no way to write a URL that will cause
your client to send something that doesn't start with /.
