Re: initial "relative-looking" elements.
"Roy T. Fielding" <email@example.com> Fri, 02 May 1997 01:56 UTC
Received: from cnri by ietf.org id aa03657; 1 May 97 21:56 EDT
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa22878; 1 May 97 21:56 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id VAA14889 for uri-out; Thu, 1 May 1997 21:41:17 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [22.214.171.124]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id VAA14884 for <firstname.lastname@example.org>; Thu, 1 May 1997 21:41:01 -0400 (EDT)
Received: from paris.ics.uci.edu (email@example.com [126.96.36.199]) by mocha.bunyip.com (8.8.5/8.8.5) with SMTP id VAA15577 for <firstname.lastname@example.org>; Thu, 1 May 1997 21:40:59 -0400 (EDT)
Received: from kiwi.ics.uci.edu by paris.ics.uci.edu id aa10493; 1 May 97 18:35 PDT
To: Larry Masinter <email@example.com>
Subject: Re: initial "relative-looking" elements.
In-reply-to: Your message of "Wed, 30 Apr 1997 22:42:49 PDT." <33682D59.337E@parc.xerox.com>
Date: Thu, 01 May 1997 18:34:39 -0700
From: "Roy T. Fielding" <firstname.lastname@example.org>
>Is it necessary to adjust the algorithm, or just to add some >additional algorithms for "testing broken links"? I guess what would be needed is a step after step 6g in the example algorithm, saying h) If the resulting buffer string still begins with one or more complete path segments of "..", then the reference is considered to be in error. Implementations may handle this error by retaining these components in the resolved path (i.e., treating them as part of the final URL), by removing them from the resolved path (i.e., discarding relative levels above the root), or by avoiding traversal of the reference. And the equivalent added to the abnormal example in section C.2. ....Roy [very busy on other things at the moment, which is why I haven't answered a lot of other mail]