-
Notifications
You must be signed in to change notification settings - Fork 347
begin <= end (4 <= 2) when slicing a://a
in Url::username
#397
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
Comments
I have tried (and so far failed) to find and fix this issue, here is what I have found: The variable The problem now is that the (truncated) URL is I think its a mismatch between parser and lib code, the former thinking there is no authority section and the latter thinking there is, but have too limited of an understanding of the codebase to decide which of the two is in the wrong. I do hope however that my little bughunt helps you solve the issue! Furthermore, I have found that the testcase presented in this issue is not minimal, the url |
This avoids a contradiction where the URL starts out with no host, but gets normalized into a URL where the first part of a path is interpreted as the host. Fixes servo#397
This avoids a contradiction where the URL starts out with no host, but gets normalized into a URL where the first part of a path is interpreted as the host. Fixes servo#397
This avoids a contradiction where the URL starts out with no host, but gets normalized into a URL where the first part of a path is interpreted as the host. Fixes servo#397
This avoids a contradiction where the URL starts out with no host, but gets normalized into a URL where the first part of a path is interpreted as the host. Fixes servo#397
This avoids a contradiction where the URL starts out with no host, but gets normalized into a URL where the first part of a path is interpreted as the host. Fixes servo#397
This is a willfull violation of the URL specification for serialization. It retains spec-compliance for parsing, it aligns with the behavior of Microsoft Edge, and it "fixes" an acknowledged specification bug. See whatwg/url#415 Fixes servo#397
This is a willfull violation of the URL specification for serialization. It retains spec-compliance for parsing, it aligns with the behavior of Microsoft Edge, and it "fixes" an acknowledged specification bug. See whatwg/url#415 Fixes servo#397
This is a willfull violation of the URL specification for serialization. It retains spec-compliance for parsing, it aligns with the behavior of Microsoft Edge, and it "fixes" an acknowledged specification bug. See whatwg/url#415 Fixes servo#397
Found by fuzzing.
The text was updated successfully, but these errors were encountered: