Re: Issue entered final state: How often is a broken link enc...

From: Balachander Krishnamurthy (bala@research.att.com)
Date: Mon, Jun 28 1999


Message-Id: <199906281110.HAA08302@raptor.research.att.com>
To: ETA WCA issues tracking forum <www-wca@w3.org>
Date: Mon, 28 Jun 1999 07:10:11 -0400
From: Balachander Krishnamurthy <bala@research.att.com>
Subject: Re: Issue entered final state: How often is a broken link enc... 


[i dont see how i can respond to "closed" issues from the tracking system]

             Issue: How often is a broken link encountered? [2]    
                  State: resolved  [not]

>Broken links can be detected in client and server logs by the HTTP
>status code 404 being returned to the client. 

rfc 2616 says

10.4.5 404 Not Found

   The server has not found anything matching the Request-URI. No
   indication is given of whether the condition is temporary or
   permanent. The 410 (Gone) status code SHOULD be used if the server
   knows, through some internally configurable mechanism, that an old
   resource is permanently unavailable and has no forwarding address.
   This status code is commonly used when the server does not wish to
   reveal exactly why the request has been refused, or when no other
   response is applicable.

what about "This status code is commonly used when the server does not
wish to reveal exactly why the request has been refused" part?
what might be "not found" to hapless aol users may be jolly well returned
to smart worldnet users? i don't know what percentage of times this might
happen but is the present understanding that a 404 is the same as "broken
link"?

cheers,
bala