Standards Track A. Rao Netscap - RFC Editor

RFC 2326 Real Time Streaming Protocol April 1998extension-code =Reason-Phrase =3DIGIT*RTSP status codes are extensible. RTSP applications are not requiredto understand the meaning of all registered status codes, though suchunderstanding is obviously desirable. However, applications MUSTunderstand the class of any status code, as indicated by the firstdigit, and treat any unrecognized response as being equivalent to thex00 status code of that class, with the exception that anunrecognized response MUST NOT be cached. For example, if anunrecognized status code of 431 is received by the client, it cansafely assume that there was something wrong with its request andtreat the response as if it had received a 400 status code. In suchcases, user agents SHOULD present to the user the entity returnedwith the response, since that entity is likely to include humanreadableinformation which will explain the unusual status.Codereason100 Continue all200 OK all201 Created RECORD250 Low on Storage Space RECORD300 Multiple Choices all301 Moved Permanently all302 Moved Temporarily all303 See Other all305 Use Proxy allSchulzrinne, et. al. Standards Track [Page 25]