Comments on: What Every Developer Should Know About URLs

By: Private Jet Hire

Private Jet Hire — Wed, 25 May 2011 11:44:37 +0000

great topic, i ve been particulary interested in the part concerning rare symbols

By: 

 — Thu, 31 Mar 2011 07:39:52 +0000

I ACTUALLY appeared to be very pleased to find this web-site.I wanted to thank you for your precious time for the wonderful learn!! I certainly having fun with every little bit of this and I’ve you book-marked to check out latest stuff you post.

By: John

John — Mon, 28 Mar 2011 20:11:33 +0000

World of HTML is so complex now days that even experienced programmer has a hard time to follow latest tags and ways of doing things…

By: jose

jose — Sun, 30 Jan 2011 19:59:40 +0000

QUOTE:———–
password – the other part of the authentication information for a URL, it is separated from the username by another : (colon) character. The username and password will be separated from the host by an @ (at) character. You may supply just the username or both the username and password e.g.:
ftp://some_user@blah.com/
ftp://some_user:some_path@blah.com/
—————
you meant
ftp://some_user:PSSWD@blah.com/

By: NK Roto Moulding Mould

NK Roto Moulding Mould — Mon, 20 Sep 2010 08:56:53 +0000

it was really good.

By: Dejay Clayton

Dejay Clayton — Mon, 06 Sep 2010 15:04:21 +0000

Nicholas,

That last part of the path is usually referred to as the “Extra Path” or “Path Info”. It’s not a part of the URL spec, but rather, part of the spec of servers that process URLs. For example, CGI:

http://www.w3.org/Daemon/User/CGI/Overview.html#PATH_INFO

It’s not part of the URL spec because only the server can determine if the extra path info is in fact extra information not. In your example, one server might implement “index.php” as a PHP script, and another server might have “index.php” as a regular directory that contains files to be served.

By: Lo que todo programdor debería saber sobre… | Vientos de Libertad

Lo que todo programdor debería saber sobre… | Vientos de Libertad — Mon, 16 Aug 2010 15:43:51 +0000

[...] What Every Developer Should Know About URLs [...]

By: Nicholas Hebb

Nicholas Hebb — Sun, 01 Aug 2010 22:04:24 +0000

The format that has always puzzled me are WordPress URL’s, e.g.,

http://www.somesite/blog/index.php/wtf-is-this-part-called/

What do you call that last part of the URL?

By: Al surfend over het web 12 juli | Contentgirls

Al surfend over het web 12 juli | Contentgirls — Mon, 12 Jul 2010 17:10:16 +0000

[...] Alles wat je wilt en moet weten over URL’s [...]

By: sberhan

sberhan — Thu, 24 Jun 2010 20:56:22 +0000

Great article. Interesting you pointed out the use of a semicolon as a separator in a query string. According to the W3C, it seems to be simply a recommendation to use a semicolon instead of “&” which is perhaps why a number of parsing functions in various languages (eg. php’s , .Net) are hard-coded to parse with “&” in the query string:
http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.2.2

“We recommend that HTTP server implementors, and in particular, CGI implementors support the use of “;” in place of “&” to save authors the trouble of escaping “&” characters in this manner.”
For example, see the results of parsing any URL via:

http://urlparser.com/

Besides, the purpose of the recommendation to not use “&” doesn’t help much when in fact the “&” needs to be escaped through out the value of html tag attributes. For example,
Blah is invalid. It needs to be escaped as: Blah