Hi, I am using Live555 with the "-t" flag. I checked the sockets connection status: Some are in EST (Established state) whereas some sockets are in CLOSE_WAIT or FIN_WAIT2 state. Incase of 404 Not Found, it seems like its a sockets leaking issue.
Thanks Siddhant. On Thu, Feb 27, 2020 at 1:44 AM dan_desjardins <dan.desjard...@videstra.com> wrote: > >> In any case, because this ‘problem’ occurs when there’s a “404 not > found” error (i.e. an incorrect “rtsp://“ URL was given somewhere), this > doesn’t seem like a serious issue. > > A 404 error is a perfectly valid response when an rtsp source is > unavailable (during a power failure or maintenance or a plethora of valid > issues). 404 does not mean the URL is malformed or incorrect in some way > (that's what 400 is for) - it means the source is just not there. Since > our system must automatically reconnect once the source is available, > leaking sockets seems like it is a serious issue. According to Wiki: "404 > Not Found - The requested resource could not be found but may be available > in the future. Subsequent requests by the client are permissible." > > > _______________________________________________ > live-devel mailing list > live-devel@lists.live555.com > http://lists.live555.com/mailman/listinfo/live-devel >
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
