Re: The "deprecate/fixed-base" option

> You get    http://www.w3c.org/pop_empty_stack

You might get that

> The URI specification handles that.  You can not pop off a part between //
> and the next /

True, but you can raise an error, or you might keep the ../ at least
that's what the rfc says:

      g) 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 URI), by removing them from
         the resolved path (i.e., discarding relative levels above the
         root), or by avoiding traversal of the reference.


David

Received on Wednesday, 14 June 2000 17:47:47 UTC