New issue
Advanced search Search tips

Issue 694959 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Jan 10
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

KURL url parsing does not parse host correctly when using a non standard scheme

Project Member Reported by andypaicu@chromium.org, Feb 22 2017 
Chrome Version: 58.0.3021.0
OS: All

What steps will reproduce the problem?

Parsing "non-standard-scheme://a.com" will parse the host component
as "" instead of "a.com".
Parsing "non-standard-scheme://a.com/" parses the host correctly

See https://codereview.chromium.org/2705193003 for a test that fails because of this behaviour.
Project Member

Comment 1 by bugdroid1@chromium.org, Feb 24 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9ad590d1e5dd205d13f39a6bff4795732d3be55a

commit 9ad590d1e5dd205d13f39a6bff4795732d3be55a
Author: andypaicu <andypaicu@chromium.org>
Date: Fri Feb 24 10:25:40 2017

Investigated cause of failing tests for non-standard-scheme matching

Turns out it's caused by incorrect url parsing. The host is returned as ""
in this particular scenario. Raised bug for this.

BUG= 692449 , 694959 

Review-Url: https://codereview.chromium.org/2705193003
Cr-Commit-Position: refs/heads/master@{#452787}

[modify] https://crrev.com/9ad590d1e5dd205d13f39a6bff4795732d3be55a/third_party/WebKit/Source/core/frame/csp/CSPSourceTest.cpp

Comment 2 by benhenry@google.com, Jan 10

Status: Archived (was: Untriaged)
Archiving P3s older than 1 year with no owner or component.
►

Sign in to add a comment