Standards Track A. Rao Netscap - RFC Editor

RFC 2326 Real Time Streaming Protocol April 199811.3 Client Error 4xx11.3.1 405 Method Not AllowedThe method specified in the request is not allowed for the resourceidentified by the request URI. The response MUST include an Allowheader containing a list of valid methods for the requested resource.This status code is also to be used if a request attempts to use amethod not indicated during SETUP, e.g., if a RECORD request isissued even though the mode parameter in the Transport header onlyspecified PLAY.11.3.2 451 Parameter Not UnderstoodThe recipient of the request does not support one or more parameterscontained in the request.11.3.3 452 Conference Not FoundThe conference indicated by a Conference header field is unknown tothe media server.11.3.4 453 Not Enough BandwidthThe request was refused because there was insufficient bandwidth.This may, for example, be the result of a resource reservationfailure.11.3.5 454 Session Not FoundThe RTSP session identifier in the Session header is missing,invalid, or has timed out.11.3.6 455 Method Not Valid in This StateThe client or server cannot process this request in its currentstate. The response SHOULD contain an Allow header to make errorrecovery easier.11.3.7 456 Header Field Not Valid for ResourceThe server could not act on a required request header. For example,if PLAY contains the Range header field but the stream does not allowseeking.Schulzrinne, et. al. Standards Track [Page 42]