# Re: Source-routed URLs

Larry Masinter (masinter@parc.xerox.com)
Fri, 30 Sep 1994 22:52:43 PDT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Sally Hambridge: "URCs and IAFA templates"
- Previous message: John Labovitz: "Re: Source-routed URLs"
- Maybe in reply to: lazear@gateway.mitre.org: "Source-routed URLs"
- Next in thread: Peter J Churchyard: "Re: Source-routed URLs"

    To: www-security@ns1.rutgers.edu

    Subject: Re: Source-routed URLs

    From: Larry Masinter <masinter@parc.xerox.com>

    Message-Id: <94Sep30.225252pdt.2760@golden.parc.xerox.com>

    Date: 	Fri, 30 Sep 1994 22:52:43 PDT

> 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 /.

- Next message: Sally Hambridge: "URCs and IAFA templates"
- Previous message: John Labovitz: "Re: Source-routed URLs"
- Maybe in reply to: lazear@gateway.mitre.org: "Source-routed URLs"
- Next in thread: Peter J Churchyard: "Re: Source-routed URLs"