Issues List for the
URI Test Cases and Implementation Reports

Test Cases
nametitletypestatus
examples-in-specrelative parsing examples in section 5.4 of URIrelativeverified
percent-encoded-reg-nametest if %hh is processed correctly in reg-namepercent-encodingunverified

Tested Implementations
nametitletypestatus
uri_test.plRoy's example URI reference parserimplementationcompliant
SafariApple Safari 1.0.2implementationcompliant
HaskellUtilsGraham Klyne's Haskell Utilsimplementationcompliant
AcrobatAdobe Acrobat 6.01 web captureimplementationcompliant
AmayaW3C Amaya (current CVS)implementationnon-compliant
OperaOpera (V7.23, build 3227, Win2000)implementationnon-compliant
ChecklinkW3C Checklinkimplementationnon-compliant
FirefoxMozilla Firefox 0.8, Win XPimplementationnon-compliant
SAP Enterprise PortalSAP Enterprise Portalimplementationnon-compliant


examples-in-specrelative parsing examples in section 5.4 of URI
verifiedrelative
report: Roy T. Fielding, 19 Apr 2004, rel_examples1:
The examples provided in the specification (section 5.4) use a base
URI of "http://a/b/c/d;p?q" and should be consistent with almost all
implementations.  A rel_examples1
Test Page is provided for visual testing.  Note that this is only
a test of the URI reference parser and conversion to absolute form.
report: Martin Duerst, 20 Apr 2004, uri-rel-test.html:
I have created a testing page at http://www.w3.org/2004/04/uri-rel-test.html
to make (manual) testing of the implementations in various browsers easy.

percent-encoded-reg-nametest if %hh is processed correctly in reg-name
unverifiedpercent-encoding
report: Martin Duerst, 27 Apr 2004, W3C reg-percent:
I have added some more tests to my page at

   http://www.w3.org/2004/04/uri-rel-test.html#reg-percent

What they test is whether %hh in reg-name is dealt with according
to the spec. There are two parts, one for cases that correspond
to US-ASCII only, and the other for cases that correspond to IDN.

uri_test.plRoy's example URI reference parser
compliantimplementation
report: Roy T. Fielding, 19 Apr 2004, uri_test.pl:
This simple perl script was used by Roy to test the algorithms described
within the specification.  Usage:

  cat list-of-URI-refs.txt | perl uri_test.pl "base-URI"

Here are examples of its input and output when given the
base URI of "http://a/b/c/d;p?q".

SafariApple Safari 1.0.2
compliantimplementation
report: Roy T. Fielding, 19 Apr 2004, Apple Safari site:
Roy tested the URI reference parser on Apple Safari 1.0.2 by simple
observation of the test cases.  The results were consistent with
those of rfc2396bis except in that Safari will add a default path
of "/" to http URIs that have an empty path.  Since that is consistent
with a scheme-specific optimization, Safari 1.0.2 is compliant.

AmayaW3C Amaya (current CVS)
non-compliantimplementation
report: Martin Duerst, 20 Apr 2004, W3C Amaya:
I have used this page to test Amaya (my version, compiled from CVS
checkout on 2004-01-04). I don't know whether (or to what extent)
processing is done by Amaya or by libwww. Here are the results:

All tests are passed, except the following:

#       rel             correct                 Amaya

6       //g             http://g                http://g/ (additional slash)
7       ?y              http://a/b/c/d;p?y      http://a/b/c/?y (d;p removed)
9       #s              http://a/b/c/d;p?q#s    {testpage URI}#s
15                      http://a/b/c/d;p?q      not tested
43      g.              http://a/b/c/g.         http://a/b/c/g (dot removed)
51      ./../g          http://a/b/g            http://a/b/c/g (/c not removed)
55      g;x=1/./y       http://a/b/c/g;x=1/y    http://a/b/c/g;x=1/./y
                                                        (precedence of ; over /)
56      g;x=1/../y      http://a/b/c/y          http://a/b/c/g;x=1/../y
                                                        (precedence of ; over /)

For test 71, Amaya uses strict parsing.

OperaOpera (V7.23, build 3227, Win2000)
non-compliantimplementation
report: Martin Duerst, 20 Apr 2004, W3C Amaya:
All tests are passed, except the following:

#       rel             correct                 Amaya

6       //g             http://g                http://g/ (additional slash)
9       #s              http://a/b/c/d;p?q#s    {testpage URI}#s
15                      http://a/b/c/d;p?q      not tested
51      ./../g          http://a/b/g            http://a/b/c/g (/c not removed)

For test 71, Opera uses backwards-compatible parsing.

ChecklinkW3C Checklink
non-compliantimplementation
report: Martin Duerst, 20 Apr 2004, W3C Checklink:
All tests are passed, except the following:

#       relative        absolute                Link checker

6       //g             http://g                http://g/  (added slash)
7       ?y              http://a/b/c/d;p?y      http://a/b/c/?y  (missing d;p)
31      ../../../g      http://a/g              http://a/../g    (leftover ../)
32      ../../../../g   http://a/g              http://a/../../g (leftover ./../)
41      /./g            http://a/g              http://a/./g     (leftover ./)
51      ./../g          http://a/b/g            http://a/b/c/g   (leftover c/)

For test 71, the link checker uses strict parsing.

FirefoxMozilla Firefox 0.8, Win XP
non-compliantimplementation
report: Mark Baker, 20 Apr 2004, Mozilla Firefox:
#       rel             correct                 Firefox 0.8

6       //g             http://g                http://g/
15                      http://a/b/c/d;p?q      not testable
51      ./../g          http://a/b/g            http://a/b/c/g
71	http:g					http://a/b/c/g

HaskellUtilsGraham Klyne's Haskell Utils
compliantimplementation
report: Graham Klyne, 20 Apr 2004, HaskellUtils:
passes all tests.

SAP Enterprise PortalSAP Enterprise Portal
non-compliantimplementation
report: Graham Klyne, 20 Apr 2004, :
rel		correct			SAP EP KM

?y        http://a/b/c/d;p?y      http://a/b/c/?y
http:g    http:g                  http://a/b/c/g
http:     http:                   not accepted as vaid URI or URI Reference

AcrobatAdobe Acrobat 6.01 web capture
compliantimplementation
report: Graham Klyne, 29 Apr 2004, http://www.adobe.com/:
Adobe Acrobat 6.01 'web capture' on 

 http://gbiv.com/protocols/uri/test/rel_examples1.html

produces a PDF file with URIs that agree with [R] except:

   http:g   http://a/b/c/g          (ok for compat.)
   http:    http://a/b/c/d;p?q      (ok for compat.)

   /./g     http://a/./g            [X]
   /../g    http://a/../g           [X]

Note RFC2396bis [R] and RFC2396 [X] agree except in three
test cases:   ?y,  /./g,  /../g.