Re: [whatwg/url] Strictness on Port doesn't conform to URL/URI RFCs (Issue #883)

TechnicallyWeb3 left a comment (whatwg/url#883)

> That's flat out incorrect. In fact, the opposite happens. Th

No _you're_ flat out incorrect. 

I'd challenge you to beat my logic:

```
const original = 'wttp://site-admin.1:0x1234@blog.my-little-pony.eth:11155111/help.html'
const full = original.split('://')[1]
const authority = full.split('/')[0]
// site-admin.1:0x1234@blog.my-little-pony.eth:11155111
const userInfo = authority.split('@')[0]
// site-admin.1:0x1234
const username = userInfo.split(':')[0]
// site-admin.1
```

vs 

```
const original = 'wttp://site-admin.1-0x1234-blog.my-little-pony.eth-11155111/help.html'
const full = original.split('://')[1]
const authority = full.split('/')[0]
// site-admin.1-0x1234-blog.my-little-pony.eth-11155111
const urlParts = full.split('-')
// [site, admin.1, 0x1234, blog.my, little, pony.eth, 11155111]
```
Good luck determining what's part of the host, user and port... Congrats your parsing complexity has just risen significantly!

It's like trying to organize blocks by using blocks as the delimiter. 

But this is a different issue from port number limitations. I encourage you to open a new issue with the proof that parsing URLs using `-` or `.` is more efficient than special delimiters for the various parts of the URL. Good luck. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/883#issuecomment-3368433028
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/883/3368433028@github.com>