W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2003

Re: HTTP substatus error codes (403.9, 500.20, etc.)

From: Alex Rousskov <rousskov@measurement-factory.com>
Date: Sun, 23 Mar 2003 14:06:56 -0700 (MST)
To: Larry Masinter <LMM@acm.org>
cc: ietf-http-wg@w3.org
Message-ID: <Pine.BSF.4.53.0303231357430.42662@measurement-factory.com>

On Sun, 23 Mar 2003, Larry Masinter wrote:

> IIS has a feature for "substatus" error codes, at least according to
> the document I can find, but how are these communicated back to the
> client?

I am not a Microsoft user or administrator, but according to [1],
substatus error codes are NOT communicated back to the client.
According to the information I could find, these codes are used on the
server side only, to customize the content of error messages
(generated by a customized server) or to provide server admins more
info (through server log files).

Hopefully, somebody with first-hand IIS knowledge will respond to
confirm or deny the above.

> One of the complaints about HTTP error messages is that they're not
> very extensible, but it looks like the "substatus error codes" is
> some kind of extensibility message.

The content of an error message is fully "extensible". HTTP does not
even define what the content should be! The status codes themselves
are as extensible as an integer code can be. Several popular protocols
(WebDAV, ICAP?) use extension codes to implement protocol-specific



[1] http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/server/log_substatus.asp

                            | HTTP performance - Web Polygraph benchmark
www.measurement-factory.com | HTTP compliance+ - Co-Advisor test suite
                            | all of the above - PolyBox appliance
Received on Sunday, 23 March 2003 16:07:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:36 UTC