W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 1997

HTTP status codes

From: Henning Schulzrinne (BL) <hgs@cs.columbia.edu>
Date: Wed, 23 Jul 1997 16:17:22 -0400
Message-Id: <33D666D2.6C52@cs.columbia.edu>
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Cc: confctrl@isi.edu
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/3877
I brought this up at the San Jose meeting, but there never was a
satisfactory (official) answer, as far as I remember.

SIP and RTSP re-use a number of HTTP status codes, among other
properties. It is likely that they may need to or want to adopt other
HTTP status codes that emerge in the future. Thus, it is desirable that
the SIP and RTSP-specific status codes do not conflict with HTTP codes.

One possible solution: Declare officially that HTTP will only use status
codes up to x49 (say) and leave others for private extensions, including

(Note to HTTP-WG: SIP and RTSP are described, inter alia, at  and
http://www.cs.columbia.edu/~hgs/rtsp and

Comments and decisions are appreciated.

Henning Schulzrinne         email: schulzrinne@cs.columbia.edu
Dept. of Computer Science   phone: +1 908 949 8344 (at Bell Labs)
Columbia University         fax:   +1 212 666-0140
New York, NY 10027          URL:   http://www.cs.columbia.edu/~hgs
Received on Wednesday, 23 July 1997 13:27:45 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:03 UTC