It is a response to a get parameter. The response is a 404 Not found with a
content-length of 316
But live555 doesn't read the 316 bytes length body of the response.
So when the library is reading again the socket, it reads the body of the
previous response, and doesn't find \r\n\r\n, so it blocks.
The problem is in RTSPClient.cpp in getMediaSessionParameter
function, when you
check the responseCode (line 1572). If it's != 200 then you don't
read the body
of the message, which stays in the socket.
Don't you think we should read the response body, whatever the response code ?
I suppose so, although it's strange that the response has additional
content following the "404 Not found" response header. However, in
the spirit of "be liberal in what you accept", we should check for
(and discard) this extra data. I'll make this change in a future
release of the code.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
