-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
strip ascii tab/newline from urls before protocol check #21433
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
Open
rootvector2
wants to merge
1
commit into
emberjs:main
Choose a base branch
from
rootvector2:strip-url-control-chars
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+5
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
i didn't know this! do you have a link to a spec or something here? or... why don't we use
URL's parse?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.
It's in the WHATWG URL parser itself: step 2 of the basic URL parser says "Remove all ASCII tab or newline from input," where ASCII tab or newline is U+0009, U+000A, U+000D (https://url.spec.whatwg.org/#url-parsing). So
new URL('java\nscript:alert(1)').protocolalready comes back asjavascript:. Node's legacyurl.parsepredates that and keeps the characters, so it reports a null protocol instead.On using
URL's parse here: we can't on this branch. This is the fastboot path, and fastboot sets theURLglobal to node'srequire('url')module, soURLisn't the WHATWG constructor anymore (that's what the comment above and theweirdURL.parseobject check are detecting). The non-fastbootelsebranch does usenew URL()and already gets this for free. Stripping the chars here just mirrors that behavior until fastboot stops shadowing the global.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.
would that make node's URL constructor wrong? I already have an RFC around some phrasing around "SSR environments need to properly implement a rendering env"
emberjs/rfcs#1178
would love your feedback.
the main goal I have is to remove all non-standard codepaths in the codebase, so that we can:
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.
Node's WHATWG
URLconstructor isn't wrong, it strips those per spec. The non-standard bits are the legacyurl.parseand the fact that fastboot swaps theURLglobal for the oldrequire('url')module, so this branch can't reach the spec-compliant parser. If the RFC gets SSR envs to stop shadowingURL, this whole legacy branch and this patch go away with it, so the direction lines up with what you want. I'll leave some notes on the RFC. Happy to keep this as a stopgap until then.