urls containing multiple protocols not parsed correctly
Reported by
jonathan...@googlemail.com,
Sep 16
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Example URL: http://ftp://192.168.178.39 Steps to reproduce the problem: 1. type in url http://ftp://192.168.178.39 2. enter 3. What is the expected behavior? got to ftp://192.168.178.39 What went wrong? the ":" is missing in the new url Did this work before? N/A Chrome version: 68.0.3440.106 Channel: stable OS Version: 10.0 Flash Version: this could also be intended behaviour for some other usecase. yes i realize this is generally not how youre supposed to use urls :D
,
Sep 18
Behaviors not specified by https://url.spec.whatwg.org/ are WontFix. Unwrapping another protocol from within http:// would be unexpected. The browsers I tested (Chrome, Firefox, Safari) agree on the current behavior, which considers that URL as having a bogus port section and hence parses to host=ftp, path=//192.168.178.39. |
||
►
Sign in to add a comment |
||
Comment 1 by phanindra.mandapaka@chromium.org
, Sep 17