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.
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
Use the url spec to parse ice server urls. #2694
Use the url spec to parse ice server urls. #2694
Changes from 2 commits
dc7e2bd
70cf5a8
c134b51
2642b20
12e6ef5
c835751
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't work as parsedURL is a data structure. How is this implemented?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This tries to preserve the existing normative language. I shold s/parsedURL/url/ again perhaps. As I mention in the OP, looking for ideas on how to specify the requirements using the URL spec. We want to prevent hierarchical urls, e.g.
stun:foo.bar.com:1234
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In Firefox, this is implemented here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That URL isn't hierarchical though, is it? Hierarchical URLs contain slashes, as far as I know.
It sounds like you want https://url.spec.whatwg.org/#url-opaque-path to be true, although you wouldn't have to check for credentials in that case.
And then as per the Firefox code you'd have to parse parsedURL's path (which will be a string in this case) in a custom manner to obtain the host and port (split on
:
, then handle each?). Potentially this logic could be shared with the URL Standard in some way.And then you'd handle the parsedURL's query as per Firefox logic for the query.