- From: olivier Thereaux <ot@w3.org>
- Date: Thu, 26 Oct 2006 10:59:01 +0900
- To: "Miller, Ryan" <ryan.miller@sap.com>
- Cc: <www-validator@w3.org>
Dear Ryan. On Oct 26, 2006, at 03:13 , Miller, Ryan wrote: > I recently tried validating the http://www.cfmueller.com/ url. Checking links, not validating. Validating is done by another tool talked about on this same list, so it's better to avoid confusion. > 403 <> 1 The link is forbidden! This needs fixing. Usual > suspects: a missing index.html or Overview.html, or a missing ACL. > http://www.cfmueller.com/resume.html Generally speaking, if the link checker says it has been barred access to a resource, you can safely trust that the resource was indeed forbidden to the link checker. > If I click on the link, it resolves and shows in the browser. I > checked > with my hosting company and they do not have any special ACL settings. This is not a problem with the link checker but with your server. Your server is refusing HEAD HTTP methods. This is the standard way which the link checker uses to check whether a resource exists. HEAD http://www.cfmueller.com/resume.html 403 Forbidden Date: Thu, 26 Oct 2006 01:55:56 GMT Server: Microsoft-IIS/6.0 Content-Length: 1052 Content-Type: text/html Client-Date: Thu, 26 Oct 2006 01:55:55 GMT Client-Peer: 64.34.236.155:80 Client-Response-Num: 1 MicrosoftOfficeWebServer: 5.0_Pub X-Powered-By: ASP.NET Please check the archives of this mailing-list, I'm sure the question of how to fix ASP.NET servers to accept HEAD requests has been addressed in the past. Hope this helps. olivier -- olivier Thereaux - W3C - http://www.w3.org/People/olivier/ W3C Open Source Software: http://www.w3.org/Status
Received on Thursday, 26 October 2006 01:59:16 UTC