This repository has been archived by the owner on May 17, 2023. It is now read-only.
TransportParser order restriction (via feature branch) #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the TransportParser is very restrictive in the order that transport values are parsed. In the RFC spec there appears to be no set order on how client_port,server_port, and source are ordered.
For that matter the entire string except for the very beginning is order independent. Currently in order to get specs passing with a real server "Wowza" I have just per-mutated client_port,server_port, and source.
Wowza helped me discover this issue as their server puts client_port ahead of source. If the URL to the Wowza server is broken, there are plenty of rtsp servers to try from the "RTSP Player" Android App via Channel list.