W3C home > Mailing lists > Public > www-validator-cvs@w3.org > May 2011

2008/link-testsuite index.html,1.8,1.9

From: Ville Skytta via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 23 May 2011 19:57:25 +0000
To: www-validator-cvs@w3.org
Message-Id: <E1QObFl-0005i7-Ci@lionel-hutz.w3.org>
Update of /sources/public/2008/link-testsuite
In directory hutz:/tmp/cvs-serv21858

Modified Files:
	index.html 
Log Message:
<base href> are intentionally dereferenced, don't expect a 404 for a broken one.


Index: index.html
===================================================================
RCS file: /sources/public/2008/link-testsuite/index.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- index.html	11 Mar 2010 20:11:05 -0000	1.8
+++ index.html	23 May 2011 19:57:23 -0000	1.9
@@ -30,6 +30,49 @@
 </p>
 
 
+<h3>Base URI and Content-Location Tests</h3>
+<p>Does the checker respect base href and content-location info? Does it report broken links based on those?</p>
+ 
+    <h4>test base URI with BASE href elt</h4>
+    <p><a href="http://qa-dev.w3.org/link-testsuite/base-1.html">tested document</a></p>
+<p>    relative link goes 404 if BASE href element not parsed
+	EXPECTED: relative link goes 200 if OK - link checker finds no error
+    </p>
+    
+ 
+    <h4>test base URI with HTTP Content-Location</h4>
+    <p><a href="http://qa-dev.w3.org/link-testsuite/base-2.php">tested document</a></p>
+<p>    relative link goes 404 if HTTP Content-Location not parsed
+    	EXPECTED: relative link goes 200 if OK - link checker finds no error</p>
+    
+ 
+    <h4>test base URI with BASE href elt and Content-Location</h4>
+    <p><a href="http://qa-dev.w3.org/link-testsuite/base-3.php">tested document</a></p>
+<p>    with both BASE href elt and HTTP Content-Location
+    	href takes precedence http://www.w3.org/TR/html401/struct/links.html#h-12.4.1
+    	relative link goes 404 if neither BASE nor Content-Location respected
+    	relative link goes 403 if HTTP Content-Location respected instead of BASE
+    	EXPECTED: relative link goes 200 if OK - link checker finds no error</p>
+    
+ 
+    <h4>test base URI with relative BASE href (forbidden)</h4>
+    <p><a href="http://qa-dev.w3.org/link-testsuite/base-4.html">tested document</a></p>
+<p>    
+        This document has a bogus BASE href value. Per the spec:
+            <q cite="http://www.w3.org/TR/html401/struct/links.html#h-12.4">This attribute specifies an <strong>absolute URI</strong> that acts as the base URI for resolving relative URIs.</q>
+    </p>
+    
+ 
+    <h4>test base URI with BASE href elt and Content-Base</h4>
+    <p><a href="http://qa-dev.w3.org/link-testsuite/base-5.php">tested document</a></p>
+<p>    with both BASE href elt and HTTP Content-Base
+    	href takes precedence http://www.w3.org/TR/html401/struct/links.html#h-12.4.1
+    	relative link goes 404 if neither BASE nor Content-Base respected
+    	relative link goes 403 if HTTP Content-Base respected instead of BASE
+    	EXPECTED: relative link goes 200 if OK - link checker finds no error</p>
+    
+ 
+
 <h3>HTML 4.01 URI attribute values Tests</h3>
 <p>Testing whether the checker catches 404 for all attributes values set to %URI type in HTML 4.01</p>
  
@@ -59,7 +102,7 @@
     <p><a href="http://qa-dev.w3.org/link-testsuite/html_base_href_b.html">tested document</a></p>
 <p>    
         BASE href 404
-        	EXPECTED: link checker throws error
+        	EXPECTED: link checker does not throw error (not dereferenced)
     </p>
     
  
@@ -292,49 +335,6 @@
     
  
 
-<h3>Base URI and Content-Location Tests</h3>
-<p>Does the checker respect base href and content-location info? Does it report broken links based on those?</p>
- 
-    <h4>test base URI with BASE href elt</h4>
-    <p><a href="http://qa-dev.w3.org/link-testsuite/base-1.html">tested document</a></p>
-<p>    relative link goes 404 if BASE href element not parsed
-	EXPECTED: relative link goes 200 if OK - link checker finds no error
-    </p>
-    
- 
-    <h4>test base URI with HTTP Content-Location</h4>
-    <p><a href="http://qa-dev.w3.org/link-testsuite/base-2.php">tested document</a></p>
-<p>    relative link goes 404 if HTTP Content-Location not parsed
-    	EXPECTED: relative link goes 200 if OK - link checker finds no error</p>
-    
- 
-    <h4>test base URI with BASE href elt and Content-Location</h4>
-    <p><a href="http://qa-dev.w3.org/link-testsuite/base-3.php">tested document</a></p>
-<p>    with both BASE href elt and HTTP Content-Location
-    	href takes precedence http://www.w3.org/TR/html401/struct/links.html#h-12.4.1
-    	relative link goes 404 if neither BASE nor Content-Location respected
-    	relative link goes 403 if HTTP Content-Location respected instead of BASE
-    	EXPECTED: relative link goes 200 if OK - link checker finds no error</p>
-    
- 
-    <h4>test base URI with relative BASE href (forbidden)</h4>
-    <p><a href="http://qa-dev.w3.org/link-testsuite/base-4.html">tested document</a></p>
-<p>    
-        This document has a bogus BASE href value. Per the spec:
-            <q cite="http://www.w3.org/TR/html401/struct/links.html#h-12.4">This attribute specifies an <strong>absolute URI</strong> that acts as the base URI for resolving relative URIs.</q>
-    </p>
-    
- 
-    <h4>test base URI with BASE href elt and Content-Base</h4>
-    <p><a href="http://qa-dev.w3.org/link-testsuite/base-5.php">tested document</a></p>
-<p>    with both BASE href elt and HTTP Content-Base
-    	href takes precedence http://www.w3.org/TR/html401/struct/links.html#h-12.4.1
-    	relative link goes 404 if neither BASE nor Content-Base respected
-    	relative link goes 403 if HTTP Content-Base respected instead of BASE
-    	EXPECTED: relative link goes 200 if OK - link checker finds no error</p>
-    
- 
-
 <h3>HTTP Error codes test</h3>
 <p>Testing whether the checker reports all possible kinds of HTTP errors (4xx and 5xx)</p>
  
@@ -497,7 +497,7 @@
 
 
 		<p class="copyright">
-			Copyright &copy; 2010
+			Copyright &copy; 2011
 			W3C&reg;
 
 			(MIT,
Received on Monday, 23 May 2011 19:57:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:45 UTC