3 ms·

Fragment identifiers are not sent to the server. query example should have both ? and & like ?foo=1&bar=2&baz=3 Perhaps behind the path/to/whatever have

by 6510 3y ago

Fragment identifiers are not sent to the server. query example should have both ? and & like ?foo=1&bar=2&baz=3 Perhaps behind the path/to/whatever have a /filename.XXX Also, the story on the www "subdomain" is missing.

samtho 3y ago
For the query portion, it really depends if your are reading it server side or client side and using the WHATWG standard[0] which itself just mirrors convention. However, the standard dictating how a URL might be formed does not mandate anything about the query string that makes it parsable. [0]: https://url.spec.whatwg.org/#interface-urlsearchparams https://url.spec.whatwg.org/#interface-urlsearchparams
whatbackup 3y ago
Hello, author here, thank you for your feedback. > Fragment identifiers are not sent to the server. I've not stated that this is the case, but I might add a note, that this is the case. > query example should have both ? and & like > ?foo=1&bar=2&baz=3 The `&` is only needed if you have multiple parameters like in the Youtube example, or am I getting it wrong? > Perhaps behind the path/to/whatever have a /filename.XXX This is an example for a path without explicit resource as most servers would provide an `index.html` file by default in this case. I might add a note to clarify it. > Also, the story on the www "subdomain" is missing. Story, as in history?
- 6510 3y ago
  The page is wonderful as is but nothing is ever perfect. I think the page has 3 different readers: 1) quickly figure out how url's work (without the useless username:password@ and the port number) 2) The full spec/technical description. 3) The elaborate: Everything there is to know about this, history use cases etc. I remember when it was normal to have data structures separated by whatever character. Sometimes you needed multiple or (heaven forbid) more than one character. It wasn't always as pretty as one would like. The URL is the worse case with all this "://",":", ".", "@", "/", "?", "&", "#" which may have a different meaning depending on where they are found. It is now complex enough to challenge even the best of us. I keep making this joke no one thinks is funny: how embarrassing it is to have to explain this to the youngsters. We can only hope they are naive enough not to loudly protest our compound mistakes. Imagine how the reader is assumed to know the "[notation]" for optional parts but then "we" chose to wrap the ipv6 in it! Or take how it isn't mailto:// nor https:www.example.com I'm not entirely sure but I think it was www as opposed to ftp.example.com or mail, smpt, pop? The www was the new thing on the internet. > I've not stated that this is the case, but I might add a note, that this is the case. It is never mentioned on pages like yours but seems interesting perhaps even useful to know. > The `&` is only needed if you have multiple parameters What samtho wrote below is interesting. Apparently it is just convention. You can do whatever you like (as long as it doesn't include a "#" I presume) You could say: scheme://username:password@hostname:port/path?query#fragment But then it would be less obvious than something like: http ://jack:agent007@mywebsite.com:80/vacation/antartica/temprature.php?year=1988&month=march#notes Except the username:password and the port people are likely to have seen most parts browsing the web.
Jasper_ 3y ago
The a=b&c=d syntax is part of application/x-www-url-formencoded which was a Mosaic invention, and came after query strings. [0] [1] [0] http://1997.webhistory.org/www.lists/www-talk.1993q3/0812.html http://1997.webhistory.org/www.lists/www-talk.1993q3/0812.ht... [1] https://web.archive.org/web/19961220100435/http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/Docs/fill-out-forms/overview.html https://web.archive.org/web/19961220100435/http://www.ncsa.u...
Biganon 3y ago
Also, what's with ";" as a delimiter in the query? I would've appreciated an example

by 6510 3y ago

samtho 3y ago

For the query portion, it really depends if your are reading it server side or client side and using the WHATWG standard[0] which itself just mirrors convention. However, the standard dictating how a URL might be formed does not mandate anything about the query string that makes it parsable. [0]: https://url.spec.whatwg.org/#interface-urlsearchparams https://url.spec.whatwg.org/#interface-urlsearchparams

whatbackup 3y ago

Hello, author here, thank you for your feedback. > Fragment identifiers are not sent to the server. I've not stated that this is the case, but I might add a note, that this is the case. > query example should have both ? and & like > ?foo=1&bar=2&baz=3 The `&` is only needed if you have multiple parameters like in the Youtube example, or am I getting it wrong? > Perhaps behind the path/to/whatever have a /filename.XXX This is an example for a path without explicit resource as most servers would provide an `index.html` file by default in this case. I might add a note to clarify it. > Also, the story on the www "subdomain" is missing. Story, as in history?

6510 3y ago
The page is wonderful as is but nothing is ever perfect. I think the page has 3 different readers: 1) quickly figure out how url's work (without the useless username:password@ and the port number) 2) The full spec/technical description. 3) The elaborate: Everything there is to know about this, history use cases etc. I remember when it was normal to have data structures separated by whatever character. Sometimes you needed multiple or (heaven forbid) more than one character. It wasn't always as pretty as one would like. The URL is the worse case with all this "://",":", ".", "@", "/", "?", "&", "#" which may have a different meaning depending on where they are found. It is now complex enough to challenge even the best of us. I keep making this joke no one thinks is funny: how embarrassing it is to have to explain this to the youngsters. We can only hope they are naive enough not to loudly protest our compound mistakes. Imagine how the reader is assumed to know the "[notation]" for optional parts but then "we" chose to wrap the ipv6 in it! Or take how it isn't mailto:// nor https:www.example.com I'm not entirely sure but I think it was www as opposed to ftp.example.com or mail, smpt, pop? The www was the new thing on the internet. > I've not stated that this is the case, but I might add a note, that this is the case. It is never mentioned on pages like yours but seems interesting perhaps even useful to know. > The `&` is only needed if you have multiple parameters What samtho wrote below is interesting. Apparently it is just convention. You can do whatever you like (as long as it doesn't include a "#" I presume) You could say: scheme://username:password@hostname:port/path?query#fragment But then it would be less obvious than something like: http ://jack:agent007@mywebsite.com:80/vacation/antartica/temprature.php?year=1988&month=march#notes Except the username:password and the port people are likely to have seen most parts browsing the web.

Jasper_ 3y ago

The a=b&c=d syntax is part of application/x-www-url-formencoded which was a Mosaic invention, and came after query strings. [0] [1] [0] http://1997.webhistory.org/www.lists/www-talk.1993q3/0812.html http://1997.webhistory.org/www.lists/www-talk.1993q3/0812.ht... [1] https://web.archive.org/web/19961220100435/http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/Docs/fill-out-forms/overview.html https://web.archive.org/web/19961220100435/http://www.ncsa.u...

Biganon 3y ago

Also, what's with ";" as a delimiter in the query? I would've appreciated an example