Chrome can't type port over 65535
Reported by
paul.wr...@gmail.com,
Jul 3 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.84 Safari/537.36 Steps to reproduce the problem: 1. type url, with port higher than 65535 (eg http://localhost:808080/) 2. auto removes "browse" option 3. auto sets search What is the expected behavior? browse to url with port higher than 65535 (http://localhost:808080/) What went wrong? There is an error in the port check, removing the ability to manually browse to higher port #. Unless it is already in history (cache?), cause buy server redirect. Did this work before? N/A Chrome version: 56.0.2924.84 Channel: n/a OS Version: Raspbian Jessie Flash Version: Shockwave Flash 11.2 r999 There is an error in the port check, because something weird also happens when editing urls in Bookmark Manager
,
Jul 4 2017
This is working as intended. URLs are not allowed to have a port higher than 65535; if you type a URL with a high port, it simply fails to parse as a URL, so Chrome interprets it as a plain text string (hence offering to search for the string, but not browse to it). See https://url.spec.whatwg.org/#port-state: "If port is greater than 2^16 − 1, validation error, return failure." > There is an error in the port check, removing the ability to manually browse to higher port #. There is no such thing as a higher port number. TCP packets physically cannot transmit to a port higher than 65535 so this wouldn't work even if it somehow parsed as a valid URL. #1: > "Web Share: share should throw TypeError if URL is invalid" The example I gave there deliberately uses an invalid URL to trigger an error. |
||
►
Sign in to add a comment |
||
Comment 1 by paul.wr...@gmail.com
, Jul 3 2017