-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid RTSP session header parser #9254
Comments
It's likely the server is not following the RTSP spce, to diagnose, please provide a log of RTSP messages. Add logs at Line 182 in b2333c8
and ExoPlayer/library/rtsp/src/main/java/com/google/android/exoplayer2/source/rtsp/RtspClient.java Line 423 in b2333c8
The easiest way is to use
|
|
Will be fixed soon |
Issue: #9254 #minor-release We used to allow only alphanumerical characters in session id. The spec also allows "$", "-", "_", ".", "+" (RFC2326 Sections 3.4 and 15.1). PiperOrigin-RevId: 388873742
Issue: #9254 #minor-release We used to allow only alphanumerical characters in session id. The spec also allows "$", "-", "_", ".", "+" (RFC2326 Sections 3.4 and 15.1). PiperOrigin-RevId: 388873742
I think the original regex was supposed to parse the ";timeout=X" part at the end which some devices use. The current regex returns the timeout parameter as a part of the session id causing a mismatch and the timeout parameter is not parsed at all. As an example "parseSessionHeader" function with the "headerValue" "45266830;timeout=5" returns "sessionId" as "45266830;timeout=5" where it should be "45266830" and returns the default timeout. |
The lib version is 2.14.2.
The player can't parse a RTSP session header.
It looks like the regex SESSION_HEADER_PATTERN needs to be changed.
The text was updated successfully, but these errors were encountered: