You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the cameras that we connect to using RTSP protocol was hanging indefinitely and causing a timeout. Looking at the Wireshark captures, we saw that the TCP connection was successfully established and afterwards the OPTIONS RTSP request was also ACK'ed, but server wasn't replying to the OPTIONS request. After comparing the packet captures with ffprobe, we saw that OPTIONS request was being sent to path / with gortsplib but ffprobe was sending it to the actual camera path /stream24&channel0.
This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.
One of the cameras that we connect to using RTSP protocol was hanging indefinitely and causing a timeout. Looking at the Wireshark captures, we saw that the TCP connection was successfully established and afterwards the
OPTIONS
RTSP request was also ACK'ed, but server wasn't replying to theOPTIONS
request. After comparing the packet captures withffprobe
, we saw thatOPTIONS
request was being sent to path/
withgortsplib
butffprobe
was sending it to the actual camera path/stream24&channel0
.In the RFC-7826, it says:
I checked the code and found that in connclient.go#L359
Path
field ofURL
object used inOPTIONS
request was set to"/"
instead of being set tou.Path
.Is there a specific reason to this? If not I can send a PR to fix it.
The text was updated successfully, but these errors were encountered: