2 ms·
Is there any reason we couldn't just use that anyway?
by ErroneousBosh 4mo ago
Is there any reason we couldn't just use that anyway?
- echoangle 4mo agoI think some browsers display the query params muted compared to the part before (or maybe I’m confusing it with the behavior that the domain is highlighted to prevent phishing?). But technically, you can just parse the request url however you want. I also think it shouldn’t matter with regards to any caching layers inbetween.
- TRiG_Ireland 4mo agoIf you're relying on HTML forms being filled in to generate queries, the browser will always generate standard query parameters with a question mark and ampersands. But if you're making your own links, you can generate them however you like. Semi-colons should work fine, though you may need to write your one URL parsing functions.
- Neikius 4mo agoIirc in java I managed to parse those just fine. Ages ago though. I also recall actually seeing some web pages somewhere using semicolon, possibly IBM stuff.
- iainmerrick 4mo agoYou can use it if you want, but the browser doesn’t help you at all. It can’t automatically turn a form into a matrix URI, and it can’t do anything useful with relative matrix URIs.
- flyingshelf 4mo agoYou're saying that as if developers have cared about the platform in the past twenty years. Use JS, everything is possible, even turning a div into a link, apparently.
- kazinator 4mo agoJust one minor one why you might not want to. HTTP{S}? handling objects understand the URL parameter syntax and do parsing for you, so when you write a request handler, you are dealing with structured dictionaries of request headers and URL parameters.