4 ms·
But isn't Chrome still doing the wrong thing when given https://foo.com:443 https://foo.com:443?
by adestefan 13y ago
But isn't Chrome still doing the wrong thing when given https://foo.com:443 https://foo.com:443?
- kilovoltaire 13y agoNo, because 443 is the default port for https, so it is reset to empty string.
- adestefan 13y agoI don't see anywhere in the spec where is says that's okay to do.
- matchu 13y ago> 2. If buffer is equal to url's scheme's default port, set buffer to the empty string.
- interurban 13y ago2. If buffer is equal to url's scheme's default port, set buffer to the empty string.
- bronson 13y agoSecond link in bzbarsky's post?