error in RFC 2396 example

Something to remember for the next time it is revised.

....Roy


------- Forwarded Message

From: Miles Sabin <msabin@cromwellmedia.co.uk>
To: "'fielding@ics.uci.edu'" <fielding@ics.uci.edu>
Subject: Typo in RFC 2396?
Date: Tue, 23 Mar 1999 12:30:38 -0000

Hi,

I've been working through the relative URI resolution
mechanism in RFC 2396, and I've spotted something which 
seems a little odd. The example resolution on p.29 for,

  ?y

from,

  http://a/b/c/d;p?q

is given as,

  http://a/b/c/?y

but as far as I can make out, the resolution algorithm
suggests the result ought to be,

  http://a/b/c/d;p?y

which is the result that was given in RFC 1808. It's
also the result that both Netscape 4 and IE 4 deliver.

Given that this would be an observable change in
behaviour between the two RFCs, I'm a little surprised 
that it wasn't flagged up as such if the change really 
was intended ...

Strangely enough, Sun's badly broken java.net.URL class 
_does_ give the result specified in 2396, which makes me 
suspect that something must be wrong ;-)

Cheers,


Miles

-- 
Miles Sabin                          Cromwell Media
Internet Systems Architect           5/6 Glenthorne Mews
+44 (0)181 410 2230                  London, W6 0LJ
msabin@cromwellmedia.co.uk           England

------- End of Forwarded Message

Received on Thursday, 25 March 1999 20:49:03 UTC