URLs: It's Complicated

Re:URLs: It's Complicated by prepend on Wednesday June 23, 2021 @12:34PM (#27606437)

It doesn’t seem complicated at all. Complicated to me means difficult to understand. This just involves reading the spec and it all seems pretty simple and consistent.

Complicated doesn’t mean “new to me.” If I haven’t read a man page, that doesn’t mean the command is complicated.

[ Parent | on HN ]

Re:URLs: It's Complicated by treve on Wednesday June 23, 2021 @12:51PM (#27606681)

I'm trying to figure out what your point is. Is it a criticism of the article? Are you sharing with us that you are clever? I'm trying to give it a generous interpretation, but I'm having a hard time.

So it's not complicated to you... what made you want to share this?

[ Parent | on HN ]

Re:URLs: It's Complicated by kube-system on Wednesday June 23, 2021 @01:58PM (#27607703)

If we're being sticklers for reading the docs...

> com·pli·cat·ed | ˈkämpləˌkādəd |

> adjective

> 1 consisting of many interconnecting parts or elements

[ Parent | on HN ]

Re:URLs: It's Complicated by Stratoscope on Wednesday June 23, 2021 @01:02PM (#27606848)

> This just involves reading the spec and it all seems pretty simple and consistent.

Worth noting from the article:

> And this is one of the main take-aways here: while the URL specification prescribes or allows one thing, different clients and servers behave differently.

[ Parent | on HN ]

Re:URLs: It's Complicated by alphabet9000 on Wednesday June 23, 2021 @02:06PM (#27607825)

Even browser developers have made mistakes as a result of the complexity of the spec, resulting in things like CVE-2018-6128 [0] happening.

[0] https://bugs.chromium.org/p/chromium/issues/detail?id=841105

[ Parent | on HN ]