url-formats - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:33:28Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:33, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~URL formats~~</entry-title>~~		{{DISPLAYTITLE:URL formats}}

	URLs are often defined and represented in various systems as a set of various pieces/parts. This page documents the implicit formats from those systems.		URLs are often defined and represented in various systems as a set of various pieces/parts. This page documents the implicit formats from those systems.

Tantek: /* Python 2 */ t

2011-08-25T18:37:18Z

Python 2: t

← Older revision		Revision as of 18:37, 25 August 2011
Line 125:		Line 125:
	* '''params''' (if present, preceded by ''';''')		* '''params''' (if present, preceded by ''';''')
	* '''query''' (if present, preceded by '''?''')		* '''query''' (if present, preceded by '''?''')
	* '''fragment''' (if present, preceded by '''E''')		* '''fragment''' (if present, preceded by '''#''')

	== URI specification ==		== URI specification ==

Tantek: /* Python 2 */ note optionals

2011-08-25T18:36:32Z

Python 2: note optionals

← Older revision		Revision as of 18:36, 25 August 2011
Line 123:		Line 123:
	** '''port'''		** '''port'''
	* '''path''' - e.g. "/%7Eguido/Python.html"		* '''path''' - e.g. "/%7Eguido/Python.html"
	* '''params'''		* '''params''' (if present, preceded by ''';''')
	* '''query'''		* '''query''' (if present, preceded by '''?''')
	* '''fragment'''		* '''fragment''' (if present, preceded by '''E''')

	== URI specification ==		== URI specification ==

Tantek: /* CGI */ scheme

2011-08-25T18:28:16Z

CGI: scheme

← Older revision		Revision as of 18:28, 25 August 2011
Line 90:		Line 90:
	Terms:		Terms:
	* '''script-URI'''		* '''script-URI'''
	** '''scheme''' ~~same as SERVER_PROTOCOL~~		** '''scheme'''
	** '''://'''		** '''://'''
	** '''server-name''' - SERVER_NAME		** '''server-name''' - SERVER_NAME

Tantek: /* HTTP */ flatten one single child level

2011-08-25T17:52:05Z

HTTP: flatten one single child level

← Older revision		Revision as of 17:52, 25 August 2011
Line 39:		Line 39:
	*** '''scheme'''		*** '''scheme'''
	*** ''':'''		*** ''':'''
	*** '''relativeURI'''		*** '''relativeURI''' (typically also '''net_path''')
	~~****~~ '''net_path'''		**** '''//'''
	***** '''//'''		**** '''net_loc'''
	***** '''net_loc'''		**** '''abs_path'''
	***** '''abs_path'''		***** '''/'''
	****** '''/'''		***** '''rel_path'''
	****** '''rel_path'''		****** '''path'''
	******* '''path'''		******* '''fsegment'''
	******** '''fsegment'''		******* '''segment''' (zero or more, if present, preceded by '''/''')
	******** '''segment''' (zero or more, if present, preceded by '''/''')		****** '''params''' (if present, preceded by ''';''')
	******* '''params''' (if present, preceded by ''';''')		****** '''query''' (if present, preceded by '''?''')
	******* '''query''' (if present, preceded by '''?''')
	** '''fragment''' (if present, preceded by '''#''')		** '''fragment''' (if present, preceded by '''#''')

Tantek: why

2011-08-25T16:54:35Z

why

← Older revision		Revision as of 16:54, 25 August 2011
Line 2:		Line 2:

	URLs are often defined and represented in various systems as a set of various pieces/parts. This page documents the implicit formats from those systems.		URLs are often defined and represented in various systems as a set of various pieces/parts. This page documents the implicit formats from those systems.

			== Why ==
			While similar names are used for the various parts of a URL, it's quite surprising how much variety there is for this fundamental building block of the web.

			Why do each of these descriptions of a URL use somewhat different names (and in many cases punctuation boundaries) than the others, and how did this happen?

			Perhaps by placing them in a historical order we can make some sense of the evolution of the terminology, which has likely also diverged when adopted by different communities.

	== URL specification ==		== URL specification ==

Tantek: /* URI specification */ copy/past typo

2011-08-24T06:05:06Z

URI specification: copy/past typo

← Older revision		Revision as of 06:05, 24 August 2011
Line 136:		Line 136:
	*** '''path-rootless''' or		*** '''path-rootless''' or
	*** '''path-empty'''		*** '''path-empty'''
	* '''query''' (if present, preceded by '''"?"''') e.g. "~~/over/there~~"		* '''query''' (if present, preceded by '''"?"''') e.g. "name=ferret"
	* '''fragment''' (if present, preceded by "#") e.g. "nose"		* '''fragment''' (if present, preceded by "#") e.g. "nose"


	== Googler ==		== Googler ==

Tantek: add Python 2 urlparse parameters

2011-08-24T06:02:05Z

add Python 2 urlparse parameters

@@ Line 104: / Line 104: @@
 ** '''PATH_INFO''' - e.g. "/ponylove" (remainder of path)
 ** '''QUERY_STRING''' - e.g. "q=20%C001er&moar=kitties"
 == Googler ==

Tantek: more CGI details, and dates for each

2011-08-24T01:50:12Z

more CGI details, and dates for each

← Older revision		Revision as of 01:50, 24 August 2011
Line 57:		Line 57:
	* :port is omitted if the port is 80		* :port is omitted if the port is 80
	* empty abs_path is replaced with '''/'''		* empty abs_path is replaced with '''/'''

			== DOM ==
			1996 https://developer.mozilla.org/en/DOM/window.location#Properties

			The window.location object represent the URL of the window's page and thus also has properties (terms) for the different parts/pieces.

			Properties:

			* '''protocol''' - e.g. "http:"
			* '''host''' - e.g. "www.example.com:80"
			** '''hostname''' - e.g. "www.example.com"
			** '''port''' - e.g. "80"
			* '''pathname''' - e.g. "/search"
			* '''search''' - e.g. "?q=devmo"
			* '''hash''' - e.g. "#test"

	== CGI ==		== CGI ==
	Common Gateway Interface, specifically, Environment Variables		~1997-1999? Common Gateway Interface, specifically, Environment Variables
	~~1999?~~
	* http://tools.ietf.org/html/rfc3875		* http://tools.ietf.org/html/rfc3875
	* http://www.citycat.ru/doc/CGI/overview/env.html		* http://www.citycat.ru/doc/CGI/overview/env.html
Line 78:		Line 93:
	** '''?'''		** '''?'''
	** '''query-string''' - QUERY_STRING		** '''query-string''' - QUERY_STRING


	Environment variables:		Environment variables:
	* '''SERVER_PROTOCOL''' - not the protocol scheme, e.g. "HTTP/1.1"		* '''SERVER_PROTOCOL''' - not the protocol scheme, e.g. "HTTP/1.1"
	* '''~~HTTP_HOST~~''' or '''~~SERVER_NAME~~''' - e.g "example.com"		* '''SERVER_NAME''' or '''HTTP_HOST''' - e.g "example.com"
	* '''SERVER_PORT''' - e.g. "80"		* '''SERVER_PORT''' - e.g. "80"
	* '''REMOTE_USER''' - the username (but not password)		* '''REMOTE_USER''' - the username (but not password)
	* '''PATH''' - not the URL path, but to the web server on the system		* '''PATH''' - not the URL path, but to the web server on the system
	* '''REQUEST_URI''' - e.g. "/cgi-bin/printenv.pl/ponylove?q=20%C001er&moar=kitties"		* '''REQUEST_URI''' - e.g. "/cgi-bin/printenv.pl/ponylove?q=20%C001er&moar=kitties"
	** '''SCRIPT_NAME''' - e.g. "/cgi-bin/printenv.pl"		** '''SCRIPT_NAME''' - e.g. "/cgi-bin/printenv.pl" (first two segments?)
	** '''PATH_INFO''' - e.g. "/ponylove"		** '''PATH_INFO''' - e.g. "/ponylove" (remainder of path)
	** '''QUERY_STRING''' - e.g. "q=20%C001er&moar=kitties"		** '''QUERY_STRING''' - e.g. "q=20%C001er&moar=kitties"

	~~== DOM ==~~
	* https://developer.mozilla.org/en/DOM/window.location#Properties

	~~The window.location object represent the URL of the window's page and thus also has properties (terms) for the different parts/pieces.~~

	~~Properties:~~

	* '''protocol''' - e.g. "http:"
	* '''host''' - e.g. "www.example.com:80"
	** '''hostname''' - e.g. "www.example.com"
	** '''port''' - e.g. "80"
	* '''pathname''' - e.g. "/search"
	* '''search''' - e.g. "?q=devmo"
	* '''hash''' - e.g. "#test"

	== Googler ==		== Googler ==
	Per Matt Cutts's blog post <cite>[http://www.mattcutts.com/blog/seo-glossary-url-definitions/ Talk like a Googler: parts of a url]</cite>: of for example:		2007 Per Matt Cutts's blog post <cite>[http://www.mattcutts.com/blog/seo-glossary-url-definitions/ Talk like a Googler: parts of a url]</cite>: of for example:

	<nowiki>http://video.google.co.uk:80/videoplay?docid=-7246927612831078230&hl=en#00h02m30s</nowiki>		<nowiki>http://video.google.co.uk:80/videoplay?docid=-7246927612831078230&hl=en#00h02m30s</nowiki>

Tantek: /* CGI */ link to mirror of "original" spec environment variables and include a few more details

2011-08-24T01:19:45Z

CGI: link to mirror of "original" spec environment variables and include a few more details

← Older revision		Revision as of 01:19, 24 August 2011
Line 59:		Line 59:

	== CGI ==		== CGI ==
			Common Gateway Interface, specifically, Environment Variables
			1999?
	* http://tools.ietf.org/html/rfc3875		* http://tools.ietf.org/html/rfc3875
			* http://www.citycat.ru/doc/CGI/overview/env.html
	* http://en.wikipedia.org/wiki/Common_Gateway_Interface - has example:		* http://en.wikipedia.org/wiki/Common_Gateway_Interface - has example:

Line 79:		Line 82:
	Environment variables:		Environment variables:
	* '''SERVER_PROTOCOL''' - not the protocol scheme, e.g. "HTTP/1.1"		* '''SERVER_PROTOCOL''' - not the protocol scheme, e.g. "HTTP/1.1"
	* '''HTTP_HOST''' - e.g "example.com"		* '''HTTP_HOST''' or '''SERVER_NAME''' - e.g "example.com"
	* '''SERVER_PORT''' - e.g. "80"		* '''SERVER_PORT''' - e.g. "80"
	* '''REMOTE_USER'''		* '''REMOTE_USER''' - the username (but not password)
	* '''PATH''' - not the URL path, but to the web server on the system		* '''PATH''' - not the URL path, but to the web server on the system
	* '''REQUEST_URI''' - e.g. "/cgi-bin/printenv.pl/ponylove?q=20%C001er&moar=kitties"		* '''REQUEST_URI''' - e.g. "/cgi-bin/printenv.pl/ponylove?q=20%C001er&moar=kitties"