[11678] in www-talk@info.cern.ch
Re: 404 Error "Standards"
daemon@ATHENA.MIT.EDU (Ari Gordon-Schlosberg)
Thu Aug 17 16:02:26 2000
Date: Thu, 17 Aug 2000 12:53:42 -0700
From: Ari Gordon-Schlosberg <regs@nebcorp.com>
To: "'www-talk@w3.org'" <www-talk@w3.org>
Message-Id: <20000817125341.B10989@nebcorp.com>
Mail-Followup-To: Ari Gordon-Schlosberg <regs@nebcorp.com>,
"'www-talk@w3.org'" <www-talk@w3.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <399BE7A8.C4FA09F3@w3.org>; from connolly@w3.org on Thu, Aug 17, 2000 at 08:24:56AM -0500
Resent-From: www-talk@w3.org
[Dan Connolly <connolly@w3.org>]
> "Siegel, David" wrote:
> >
> > In the process of researching how to "ping" a URL to check its validity, a
> > quick solution of just checking for a string involving "HTTP 404 Error" and
> > variations of it presented itself as a quick solution. Is there currently a
> > "default" standard for web servers for 404 errors?
>
> Er... yes; if the first 3 bytes of the response message
> are the ascii codes for '4', '0', and '4', then it's a 404 response.
No, the first three bytes should always be 'H', 'T', and 'T'. If the first
three bytes of the second token are 404, you're good to go.
HTTP-version is always the first token
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.1
>
> 6.1.1 Status Code and Reason Phrase
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1.1
--
Ari there is no spoon
-------------------------------------------------------------------------
http://www.nebcorp.com/~regs/pgp for PGP public key
