From a26e9b621ea5ba0fd88f090abc9e251c75672fa7 Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Tue, 27 Nov 2012 12:11:41 +0100 Subject: [PATCH] client: use 454 when session can't be found We should use 454 when a session can't be found because there was no session pool configured in the server. This is not a server configuration problem because the server on which the request is done might not be the same one that will keep the sessions for us and so it does not need to support sessions. --- gst/rtsp-server/rtsp-client.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gst/rtsp-server/rtsp-client.c b/gst/rtsp-server/rtsp-client.c index 94c5d4c..cd7d6a4 100644 --- a/gst/rtsp-server/rtsp-client.c +++ b/gst/rtsp-server/rtsp-client.c @@ -1271,7 +1271,7 @@ unsupported_transports: no_pool: { GST_ERROR ("client %p: no session pool configured", client); - send_generic_response (client, GST_RTSP_STS_SERVICE_UNAVAILABLE, state); + send_generic_response (client, GST_RTSP_STS_SESSION_NOT_FOUND, state); gst_rtsp_transport_free (ct); return FALSE; } @@ -1632,7 +1632,7 @@ handle_request (GstRTSPClient * client, GstRTSPMessage * request) no_pool: { GST_ERROR ("client %p: no pool configured", client); - send_generic_response (client, GST_RTSP_STS_SERVICE_UNAVAILABLE, &state); + send_generic_response (client, GST_RTSP_STS_SESSION_NOT_FOUND, &state); return; } session_not_found: -- 2.7.4