Edit count of the user ($1) (user_editcount) | 11 |
Name of the user account ($1) (user_name) | 'Harunaalkasim' |
Age of the user account ($1) (user_age) | 368765 |
Groups (including implicit) the user is in ($1) (user_groups) | [
0 => '*',
1 => 'user',
2 => 'autoconfirmed'
] |
Rights that the user has ($1) (user_rights) | [
0 => 'createaccount',
1 => 'read',
2 => 'edit',
3 => 'createtalk',
4 => 'writeapi',
5 => 'viewmywatchlist',
6 => 'editmywatchlist',
7 => 'viewmyprivateinfo',
8 => 'editmyprivateinfo',
9 => 'editmyoptions',
10 => 'abusefilter-log-detail',
11 => 'centralauth-merge',
12 => 'abusefilter-view',
13 => 'abusefilter-log',
14 => 'vipsscaler-test',
15 => 'collectionsaveasuserpage',
16 => 'reupload-own',
17 => 'move-rootuserpages',
18 => 'createpage',
19 => 'minoredit',
20 => 'editmyusercss',
21 => 'editmyuserjson',
22 => 'editmyuserjs',
23 => 'purge',
24 => 'sendemail',
25 => 'applychangetags',
26 => 'spamblacklistlog',
27 => 'mwoauthmanagemygrants',
28 => 'reupload',
29 => 'upload',
30 => 'move',
31 => 'collectionsaveascommunitypage',
32 => 'autoconfirmed',
33 => 'editsemiprotected',
34 => 'skipcaptcha',
35 => 'transcode-reset',
36 => 'createpagemainns',
37 => 'movestable',
38 => 'autoreview'
] |
Whether the user is editing from mobile app ($1) (user_app) | false |
Whether or not a user is editing through the mobile interface ($1) (user_mobile) | true |
Page ID ($1) (page_id) | 47817022 |
Page namespace ($1) (page_namespace) | 0 |
Page title without namespace ($1) (page_title) | 'URL' |
Full page title ($1) (page_prefixedtitle) | 'URL' |
Edit protection level of the page ($1) (page_restrictions_edit) | [
0 => 'autoconfirmed'
] |
Last ten users to contribute to the page ($1) (page_recent_contributors) | [
0 => 'MartinMichlmayr',
1 => 'Viko Riféo',
2 => 'Tim ThomasJnr',
3 => 'Fgnievinski',
4 => 'Hooman Mallahzadeh',
5 => 'S.Hinakawa',
6 => 'SS49',
7 => 'WhinyTheYounger',
8 => 'Matthiaspaul',
9 => 'Citation bot'
] |
Page age in seconds ($1) (page_age) | 619419119 |
Action ($1) (action) | 'edit' |
Edit summary/reason ($1) (summary) | 'HARUNA ALKASIM MIKIYA' |
Old content model ($1) (old_content_model) | 'wikitext' |
New content model ($1) (new_content_model) | 'wikitext' |
Old page wikitext, before the edit ($1) (old_wikitext) | '{{short description|Web address to a particular file or page}}
{{pp-semi-indef}}
{{other uses}}
{{Use dmy dates|date=May 2020|cs1-dates=y}}
{{Infobox technology standard
| title = URL
| long_name =Uniform Resource Locator
| native_name =
| native_name_lang =
| image =
| caption =
| status = Published
| year_started =
| version =[https://url.spec.whatwg.org Living Standard]
| version_date =2020
| preview =
| preview_date =
| organization = [[Internet Engineering Task Force]] (IETF)
| committee = [[Web Hypertext Application Technology Working Group]] (WHATWG)
| base_standards =RFC 3986. – Uniform Resource Identifier (URI): Generic Syntax. <br/>
RFC 4248. – The telnet URI Scheme. <br/>
RFC 4266. – The gopher URI Scheme. <br/>
RFC 6068. – The ‘mailto’ URI Scheme. <br/>
RFC 6196. – Moving mailserver: URI Scheme to Historic. <br/>
RFC 6270. – The ‘tn3270’ URI Scheme. <br/>
| related_standards =[[Uniform Resource Identifier|URI]], [[Uniform Resource Name|URN]]
| abbreviation = URL
| domain = [[World Wide Web]]
| license =[https://creativecommons.org/licenses/by/4.0/ CC BY 4.0]
| website = https://url.spec.whatwg.org
|first_published={{Start date and age|1994}}|authors=[[Tim Berners-Lee]]|series=Request for Comments (RFC)|editors=[[Anne van Kesteren]]}}
A '''Uniform Resource Locator''' ('''URL'''), colloquially termed a '''web address''',{{sfnp|W3C|2009}} is a reference to a [[web resource]] that specifies its location on a [[computer network]] and a mechanism for retrieving it. A URL is a specific type of [[Uniform Resource Identifier]] (URI),<ref>{{Cite web |url=https://zzz.buzz/2017/09/19/forward-and-backslashes-in-urls/ |title=Forward and Backslashes in URLs |website=zzz.buzz |language=en |access-date=19 September 2018}}</ref>{{sfnp|RFC 3986|2005}} although many people use the two terms interchangeably.{{sfnp|Joint W3C/IETF URI Planning Interest Group|2002}}{{efn|A URL implies the means to access an indicated resource and is denoted by a protocol or an access mechanism, which is not true of every URI.{{sfnp|RFC 2396|1998}}{{sfnp|Joint W3C/IETF URI Planning Interest Group|2002}} Thus <code><nowiki>http:</nowiki>//www.example.com</code> is a URL, while <code>www.example.com</code> is not.<ref>{{Cite web |url=https://danielmiessler.com/study/url-uri/#gs.Hs64zOs |title=The Difference Between URLs and URIs |author-last=Miessler |author-first=Daniel}}</ref>}} URLs occur most commonly to reference [[web page]]s ([[http]]), but are also used for file transfer ([[File Transfer Protocol|ftp]]), email ([[mailto]]), database access ([[Java Database Connectivity|JDBC]]), and many other applications.
Most [[web browser]]s display the URL of a web page above the page in an [[address bar]]. A typical URL could have the form <code><nowiki>http:</nowiki>//www.example.com/index.html</code>, which indicates a protocol (<code>http</code>), a [[hostname]] (<code>www.example.com</code>), and a file name (<code>index.html</code>).
==History==
[[File:Uniform Resource Locator.svg|thumb|Uniform Resource Locator simple example]]
Uniform Resource Locators were defined in {{IETF RFC|1738}} in 1994 by [[Tim Berners-Lee]], the inventor of the [[World Wide Web]], and the URI working group of the [[Internet Engineering Task Force]] (IETF),{{sfnp|W3C|1994}} as an outcome of collaboration started at the IETF Living Documents [[Birds of a feather (computing)|birds of a feather]] session in 1992.{{sfnp|IETF|1992}}{{sfnp|Berners-Lee|1994}}
The format combines the pre-existing system of [[domain name]]s (created in 1985) with [[Path (computing)|file path]] syntax, where [[Slash (punctuation)|slashes]] are used to separate [[Folder (computing)|directory]] and [[filename]]s. Conventions already existed where server names could be prefixed to complete file paths, preceded by a double slash (<code>//</code>).{{sfnp|Berners-Lee|2000}}
Berners-Lee later expressed regret at the use of dots to separate the parts of the [[domain name]] within [[URI]]s, wishing he had used slashes throughout,{{sfnp|Berners-Lee|2000}} and also said that, given the colon following the first component of a URI, the two slashes before the domain name were unnecessary.{{sfnp|BBC News|2009}}
An early (1993) draft of the HTML Specification<ref>{{cite techreport |title=Hypertext Markup Language (draft RFCxxx) |author-first1=Tim |author-last1=Berners-Lee |author-link1=Tim Berners-Lee |author-first2=Daniel "Dan" |author-last2=Connolly |author-link2=Daniel Connolly |date=March 1993 |page=28 |url=https://www.ucc.ie/archive/curia/dtds/html-spec.ps}}</ref> referred to "Universal" Resource Locators. This was dropped some time between June 1994 ({{IETF RFC|1630|link=no}}) and October 1994 (draft-ietf-uri-url-08.txt).<ref>{{cite techreport |title=Uniform Resource Locators (URL) |author-first1=Tim |author-last1=Berners-Lee |author-link1=Tim Berners-Lee |author-first2=Larry |author-last2=Masinter |author-link2=Larry Masinter |author-first3=Mark Perry |author-last3=McCahill |author-link3=Mark Perry McCahill |date=October 1994 |url=http://ds.internic.net/internet-drafts/draft-ietf-uri-url-08.txt}} cited in {{cite techreport |title=Constituent Component Interface++ |author-first1=C. S. |author-last1=Ang |author-first2=D. C. |author-last2=Martin |publisher=UCSF Library and Center for Knowledge Management |date=January 1995 |url=https://listserv.heanet.ie/cgi-bin/wa?A2=ind9501&L=HTML-WG&P=R23201&X=C6F9505B05BC9A3B67}}</ref>
==Syntax==
{{main|Uniform Resource Identifier#Generic syntax}}
Every HTTP URL conforms to the syntax of a generic URI. {{#section:Uniform resource identifier|syntax}}<!-- see Help:LST for how this works -->
A web browser will usually [[Uniform Resource Identifier#URI resolution|dereference]] a URL by performing an [[Hypertext Transfer Protocol|HTTP]] request to the specified host, by default on port number 80. URLs using the <code>https</code> scheme require that requests and responses be made over a [[HTTPS|secure connection to the website]].
==Internationalized URL==
Internet users are distributed throughout the world using a wide variety of languages and alphabets and expect to be able to create URLs in their own local alphabets. An Internationalized Resource Identifier (IRI) is a form of URL that includes Unicode characters. All modern browsers support IRIs. The parts of the URL requiring special treatment for different alphabets are the domain name and path.{{sfnp|W3C|2008}}{{sfnp|W3C|2014}}
The domain name in the IRI is known as an [[Internationalized Domain Name]] (IDN). Web and Internet software automatically convert the domain name into [[punycode]] usable by the Domain Name System; for example, the Chinese URL <code><nowiki>http:</nowiki>//例子.卷筒纸</code> becomes <code><nowiki>http:</nowiki>//xn--fsqu00a.xn--3lr804guic/</code>. The <code>xn--</code> indicates that the character was not originally ASCII.{{sfnp|IANA|2003}}
The URL path name can also be specified by the user in the local writing system. If not already encoded, it is converted to [[UTF-8]], and any characters not part of the basic URL character set are escaped as [[hexadecimal]] using [[percent-encoding]]; for example, the Japanese URL <code><nowiki> http:</nowiki>//example.com/引き割り.html</code> becomes <code><nowiki>http:</nowiki>//example.com/%E5%BC%95%E3%81%8D%E5%89%B2%E3%82%8A.html</code>. The target computer decodes the address and displays the page.{{sfnp|W3C|2008}}
=={{anchor|prurl}}Protocol-relative URLs==
<!--section is linked from other pages-->
Protocol-relative links (PRL), also known as protocol-relative URLs (PRURL), are URLs that have no protocol specified. For example, <code>//example.com</code> will use the protocol of the current page, typically HTTP or HTTPS.<ref>{{cite book |url=https://books.google.com/?id=6u2sBAAAQBAJ&pg=PA193 |title=Secure Development for Mobile Apps: How to Design and Code Secure Mobile Applications with PHP and JavaScript |publisher=[[CRC Press]] |author-first=J. D. |author-last=Glaser |date=2013 |page=193 |access-date=12 October 2015 |isbn=978-1-48220903-7}}</ref><ref>{{cite book |url=https://books.google.com/?id=DW0uyBZzEDwC&pg=PT124 |title=HTML, XHTML, and CSS Bible |publisher=[[John Wiley & Sons]] |author-first=Steven M. |author-last=Schafer |date=2011 |page=124 |access-date=12 October 2015 |isbn=978-1-11808130-3}}</ref>
==See also==
<!-- Please keep entries in alphabetical order & add a short description [[WP:SEEALSO]] -->
{{div col|colwidth=20em}}
* [[Hyperlink]]
* [[Persistent uniform resource locator|PURL]] - Persistent URL
* [[CURIE]] (Compact URI)
* [[Fragment identifier]]
* [[Internet Resource Locator]] (IRL)
* [[Internationalized resource identifier]] (IRI)
* [[Semantic URL]]
* [[Typosquatting]]
* [[Uniform Resource Identifier]]
* [[URL normalization]]
* [[Slash (punctuation)#Networking|Use of slashes in networking]]
{{div col end}}
<!-- please keep entries in alphabetical order -->
==Notes==
{{notelist|30em}}
==Citations==
{{reflist|30em}}
==References==
{{refbegin|30em}}
* {{cite web |url=http://news.bbc.co.uk/1/hi/technology/8306631.stm |title=Berners-Lee "sorry" for slashes |publisher=[[BBC News]] |date=14 October 2009 |access-date=14 February 2010 |ref={{SfnRef|BBC News|2009}}}}
* {{cite web |url=http://www.w3.org/Conferences/IETF92/WWX_BOF_mins.html |title=Living Documents BoF Minutes |publisher=[[World Wide Web Consortium]] |date=18 March 1992 |access-date=26 December 2011 |ref={{SfnRef|IETF|1992}}}}
* {{cite web |url=http://www.w3.org/Addressing/URL/url-spec.txt |title=Uniform Resource Locators (URL): A Syntax for the Expression of Access Information of Objects on the Network |first=Tim |last=Berners-Lee |author-link=Tim Berners-Lee |date=21 March 1994 |publisher=[[World Wide Web Consortium]] |access-date=13 September 2015 |ref={{SfnRef|W3C|1994}}}}
* {{cite IETF |rfc=1738 |title=Uniform Resource Locators (URL) |author-first1=Tim |author-last1=Berners-Lee |author-link1=Tim Berners-Lee |author-first2=Larry |author-last2=Masinter |author-link2=Larry Masinter |author-first3=Mark Perry |author-last3=McCahill |author-link3=Mark Perry McCahill |date=August 1998 |access-date=31 August 2015 |ref={{SfnRef|RFC 1738|1994}}}}
* {{cite web |url=http://www.w3.org/People/Berners-Lee/FAQ.html#etc |author-first=Tim |author-last=Berners-Lee |author-link=Tim Berners-Lee |work=Frequently asked questions |title=Why the //, #, etc? |orig-year=2000 |date=2015 |publisher=[[World Wide Web Consortium]] |access-date=3 February 2010 |ref={{SfnRef|Berners-Lee|2000}}}}
* {{cite web |url=http://www.w3.org/html/wg/href/draft#url |title=Web addresses in HTML 5 |editor-first1=Daniel "Dan" |editor-last1=Connolly |editor-link1=Daniel Connolly (computer scientist) |editor-first2=C. Michael |editor-last2=Sperberg-McQueen |editor-link2=C. Michael Sperberg-McQueen |date=21 May 2009 |publisher=[[World Wide Web Consortium]] |access-date=13 September 2015 |ref={{SfnRef|W3C|2009}}}}
* {{cite web |url=http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html |archive-url=https://web.archive.org/web/20041208124351/http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html |archive-date=8 December 2004 |title=Completion of IANA Selection of IDNA Prefix |author=Internet Assigned Numbers Authority |work=IETF-Announce mailing list |date=14 February 2003 |access-date=3 September 2015 |ref={{SfnRef|IANA|2003}} |author-link=Internet Assigned Numbers Authority}}
* {{cite IETF |rfc=2396 |title=Uniform Resource Identifiers (URI): Generic Syntax |author-first1=Tim |author-last1=Berners-Lee |author-link1=Tim Berners-Lee |author-first2=Roy T. |author-last2=Fielding |author-link2=Roy T. Fielding |author-first3=Larry |author-last3=Masinter |author-link3=Larry Masinter |date=August 1998 |access-date=31 August 2015 |ref={{SfnRef|RFC 2396|1998}}}}
* {{cite IETF |rfc=7595 |title=Guidelines and Registration Procedures for URI Schemes |editor-first=Dave |editor-last=Thaler |author-first1=Tony |author-last1=Hansen |author-first2=Ted |author-last2=Hardie |date=June 2015 |ref={{SfnRef|IETF|2015}}}}
* {{cite IETF |rfc=3305 |title=Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations |editor-first1=Michael |editor-last1=Mealling |editor-link1=Michael Mealling |editor-first2=Ray |editor-last2=Denenberg |date=August 2002 |access-date=13 September 2015 |ref={{SfnRef|Joint W3C/IETF URI Planning Interest Group|2002}}}}
* {{cite IETF |rfc=3986 |title=Uniform Resource Identifiers (URI): Generic Syntax |author-first1=Tim |author-last1=Berners-Lee |author-link1=Tim Berners-Lee |author-first2=Roy T. |author-last2=Fielding |author-link2=Roy T. Fielding |author-first3=Larry |author-last3=Masinter |author-link3=Larry Masinter |date=January 2005 |access-date=31 August 2015 |ref={{SfnRef|RFC 3986|2005}}}}
* {{cite web |title=An Introduction to Multilingual Web Addresses |url=http://www.w3.org/International/articles/idn-and-iri/|date=9 May 2008 |access-date=11 January 2015 |ref={{SfnRef|W3C|2008}}}}
* {{cite web |title=What is Happening with "International URLs" |author-first=A. |author-last=Phillip |url=https://www.w3.org/International/wiki/IRIStatus |publisher=[[World Wide Web Consortium]] |date=2014 |access-date=11 January 2015 |ref={{SfnRef|W3C|2014}}}}
* {{cite web |last1=Lawrence |first1=Eric |title=Browser Arcana: IP Literals in URLs |url=https://docs.microsoft.com/en-us/archive/blogs/ieinternals/browser-arcana-ip-literals-in-urls |website=docs.microsoft.com |accessdate=22 June 2020 |archiveurl=https://web.archive.org/web/20200622181648/https://docs.microsoft.com/en-us/archive/blogs/ieinternals/browser-arcana-ip-literals-in-urls |archivedate=22 June 2020 |language=en-us}}
{{refend}}
==External links==
* [https://url.spec.whatwg.org/ URL specification] at [[WHATWG]]
* [https://www.ibm.com/support/knowledgecenter/en/SSGMCP_4.1.0/com.ibm.cics.ts.internet.doc/topics/dfhtl_uricomp.html The Components of a URL] from [[IBM]]
{{Hypermedia}}
{{Authority control}}
[[Category:URL| ]]
[[Category:Identifiers]]
[[Category:Computer-related introductions in 1994]]' |
New page wikitext, after the edit ($1) (new_wikitext) | '{{short description|Web address to a particular file or page}}
{{pp-semi-indef}}
{{other uses}}HARUNA ALKASIM MIKIYA
{{Use dmy dates|date=May 2020|cs1-dates=y}}
{{Infobox technology standard
| title = URL
| long_name =Uniform Resource Locator
| native_name =
| native_name_lang =
| image =
| caption =
| status = Published
| year_started =2020
| version =[https://url.spec.whatwg.org Living Standard]
| version_date =2020
| preview =
| preview_date =
| organization = [[Internet Engineering Task Force]] (IETF)
| committee = [[Web Hypertext Application Technology Working Group]] (WHATWG)
| base_standards =Shi wankan tarwada ne kuma dogo
| related_standards =[[Uniform Resource Identifier|URI]], [[Uniform Resource Name|URN]]
| abbreviation = HARUNAALKASIMMIKIYA
| domain = [[World Wide Web]]
| license =[https://creativecommons.org/licenses/by/4.0/ CC BY 4.0]
| website = https://harunaalkasim mikiya.wikipedia.org
|first_published={{Start date and age|1994}}|authors=[[ HARUNA ALKASIM ADAM ]]|series=Request for Comments (RFC)|editors=[[Anne van Kesteren]]}}
A '''Uniform Resource Locator''' ('''URL'''), colloquially termed a '''web address''',{{sfnp|W3C|2009}} is a reference to a [[web resource]] that specifies its location on a [[computer network]] and a mechanism for retrieving it. A URL is a specific type of [[Uniform Resource Identifier]] (URI),<ref>{{Cite web |url=https://zzz.buzz/2017/09/19/forward-and-backslashes-in-urls/ |title=Forward and Backslashes in URLs |website=zzz.buzz |language=en |access-date=19 September 2018}}</ref>{{sfnp|RFC 3986|2005}} although many people use the two terms interchangeably.{{sfnp|Joint W3C/IETF URI Planning Interest Group|2002}}{{efn|A URL implies the means to access an indicated resource and is denoted by a protocol or an access mechanism, which is not true of every URI.{{sfnp|RFC 2396|1998}}{{sfnp|Joint W3C/IETF URI Planning Interest Group|2002}} Thus <code><nowiki>http:</nowiki>//www.example.com</code> is a URL, while <code>www.example.com</code> is not.<ref>{{Cite web |url=https://danielmiessler.com/study/url-uri/#gs.Hs64zOs |title=The Difference Between URLs and URIs |author-last=Miessler |author-first=Daniel}}</ref>}} URLs occur most commonly to reference [[web page]]s ([[http]]), but are also used for file transfer ([[File Transfer Protocol|ftp]]), email ([[mailto]]), database access ([[Java Database Connectivity|JDBC]]), and many other applications.
Most [[web browser]]s display the URL of a web page above the page in an [[address bar]]. A typical URL could have the form <code><nowiki>http:</nowiki>//www.example.com/index.html</code>, which indicates a protocol (<code>http</code>), a [[hostname]] (<code>www.example.com</code>), and a file name (<code>index.html</code>).
==History==
[[File:Uniform Resource Locator.svg|thumb|Uniform Resource Locator simple example]]
Uniform Resource Locators were defined in {{IETF RFC|1738}} in 1994 by [[Tim Berners-Lee]], the inventor of the [[World Wide Web]], and the URI working group of the [[Internet Engineering Task Force]] (IETF),{{sfnp|W3C|1994}} as an outcome of collaboration started at the IETF Living Documents [[Birds of a feather (computing)|birds of a feather]] session in 1992.{{sfnp|IETF|1992}}{{sfnp|Berners-Lee|1994}}
The format combines the pre-existing system of [[domain name]]s (created in 1985) with [[Path (computing)|file path]] syntax, where [[Slash (punctuation)|slashes]] are used to separate [[Folder (computing)|directory]] and [[filename]]s. Conventions already existed where server names could be prefixed to complete file paths, preceded by a double slash (<code>//</code>).{{sfnp|Berners-Lee|2000}}
Berners-Lee later expressed regret at the use of dots to separate the parts of the [[domain name]] within [[URI]]s, wishing he had used slashes throughout,{{sfnp|Berners-Lee|2000}} and also said that, given the colon following the first component of a URI, the two slashes before the domain name were unnecessary.{{sfnp|BBC News|2009}}
An early (1993) draft of the HTML Specification<ref>{{cite techreport |title=Hypertext Markup Language (draft RFCxxx) |author-first1=Tim |author-last1=Berners-Lee |author-link1=Tim Berners-Lee |author-first2=Daniel "Dan" |author-last2=Connolly |author-link2=Daniel Connolly |date=March 1993 |page=28 |url=https://www.ucc.ie/archive/curia/dtds/html-spec.ps}}</ref> referred to "Universal" Resource Locators. This was dropped some time between June 1994 ({{IETF RFC|1630|link=no}}) and October 1994 (draft-ietf-uri-url-08.txt).<ref>{{cite techreport |title=Uniform Resource Locators (URL) |author-first1=Tim |author-last1=Berners-Lee |author-link1=Tim Berners-Lee |author-first2=Larry |author-last2=Masinter |author-link2=Larry Masinter |author-first3=Mark Perry |author-last3=McCahill |author-link3=Mark Perry McCahill |date=October 1994 |url=http://ds.internic.net/internet-drafts/draft-ietf-uri-url-08.txt}} cited in {{cite techreport |title=Constituent Component Interface++ |author-first1=C. S. |author-last1=Ang |author-first2=D. C. |author-last2=Martin |publisher=UCSF Library and Center for Knowledge Management |date=January 1995 |url=https://listserv.heanet.ie/cgi-bin/wa?A2=ind9501&L=HTML-WG&P=R23201&X=C6F9505B05BC9A3B67}}</ref>
==Syntax==
{{main|Uniform Resource Identifier#Generic syntax}}
Every HTTP URL conforms to the syntax of a generic URI. {{#section:Uniform resource identifier|syntax}}<!-- see Help:LST for how this works -->
A web browser will usually [[Uniform Resource Identifier#URI resolution|dereference]] a URL by performing an [[Hypertext Transfer Protocol|HTTP]] request to the specified host, by default on port number 80. URLs using the <code>https</code> scheme require that requests and responses be made over a [[HTTPS|secure connection to the website]].
==Internationalized URL==
Internet users are distributed throughout the world using a wide variety of languages and alphabets and expect to be able to create URLs in their own local alphabets. An Internationalized Resource Identifier (IRI) is a form of URL that includes Unicode characters. All modern browsers support IRIs. The parts of the URL requiring special treatment for different alphabets are the domain name and path.{{sfnp|W3C|2008}}{{sfnp|W3C|2014}}
The domain name in the IRI is known as an [[Internationalized Domain Name]] (IDN). Web and Internet software automatically convert the domain name into [[punycode]] usable by the Domain Name System; for example, the Chinese URL <code><nowiki>http:</nowiki>//例子.卷筒纸</code> becomes <code><nowiki>http:</nowiki>//xn--fsqu00a.xn--3lr804guic/</code>. The <code>xn--</code> indicates that the character was not originally ASCII.{{sfnp|IANA|2003}}
The URL path name can also be specified by the user in the local writing system. If not already encoded, it is converted to [[UTF-8]], and any characters not part of the basic URL character set are escaped as [[hexadecimal]] using [[percent-encoding]]; for example, the Japanese URL <code><nowiki> http:</nowiki>//example.com/引き割り.html</code> becomes <code><nowiki>http:</nowiki>//example.com/%E5%BC%95%E3%81%8D%E5%89%B2%E3%82%8A.html</code>. The target computer decodes the address and displays the page.{{sfnp|W3C|2008}}
=={{anchor|prurl}}Protocol-relative URLs==
<!--section is linked from other pages-->
Protocol-relative links (PRL), also known as protocol-relative URLs (PRURL), are URLs that have no protocol specified. For example, <code>//example.com</code> will use the protocol of the current page, typically HTTP or HTTPS.<ref>{{cite book |url=https://books.google.com/?id=6u2sBAAAQBAJ&pg=PA193 |title=Secure Development for Mobile Apps: How to Design and Code Secure Mobile Applications with PHP and JavaScript |publisher=[[CRC Press]] |author-first=J. D. |author-last=Glaser |date=2013 |page=193 |access-date=12 October 2015 |isbn=978-1-48220903-7}}</ref><ref>{{cite book |url=https://books.google.com/?id=DW0uyBZzEDwC&pg=PT124 |title=HTML, XHTML, and CSS Bible |publisher=[[John Wiley & Sons]] |author-first=Steven M. |author-last=Schafer |date=2011 |page=124 |access-date=12 October 2015 |isbn=978-1-11808130-3}}</ref>
==See also==
<!-- Please keep entries in alphabetical order & add a short description [[WP:SEEALSO]] -->
{{div col|colwidth=20em}}
* [[Hyperlink]]
* [[Persistent uniform resource locator|PURL]] - Persistent URL
* [[CURIE]] (Compact URI)
* [[Fragment identifier]]
* [[Internet Resource Locator]] (IRL)
* [[Internationalized resource identifier]] (IRI)
* [[Semantic URL]]
* [[Typosquatting]]
* [[Uniform Resource Identifier]]
* [[URL normalization]]
* [[Slash (punctuation)#Networking|Use of slashes in networking]]
{{div col end}}
<!-- please keep entries in alphabetical order -->
==Notes==
{{notelist|30em}}
==Citations==
{{reflist|30em}}
==References==
{{refbegin|30em}}
* {{cite web |url=http://news.bbc.co.uk/1/hi/technology/8306631.stm |title=Berners-Lee "sorry" for slashes |publisher=[[BBC News]] |date=14 October 2009 |access-date=14 February 2010 |ref={{SfnRef|BBC News|2009}}}}
* {{cite web |url=http://www.w3.org/Conferences/IETF92/WWX_BOF_mins.html |title=Living Documents BoF Minutes |publisher=[[World Wide Web Consortium]] |date=18 March 1992 |access-date=26 December 2011 |ref={{SfnRef|IETF|1992}}}}
* {{cite web |url=http://www.w3.org/Addressing/URL/url-spec.txt |title=Uniform Resource Locators (URL): A Syntax for the Expression of Access Information of Objects on the Network |first=Tim |last=Berners-Lee |author-link=Tim Berners-Lee |date=21 March 1994 |publisher=[[World Wide Web Consortium]] |access-date=13 September 2015 |ref={{SfnRef|W3C|1994}}}}
* {{cite IETF |rfc=1738 |title=Uniform Resource Locators (URL) |author-first1=Tim |author-last1=Berners-Lee |author-link1=Tim Berners-Lee |author-first2=Larry |author-last2=Masinter |author-link2=Larry Masinter |author-first3=Mark Perry |author-last3=McCahill |author-link3=Mark Perry McCahill |date=August 1998 |access-date=31 August 2015 |ref={{SfnRef|RFC 1738|1994}}}}
* {{cite web |url=http://www.w3.org/People/Berners-Lee/FAQ.html#etc |author-first=Tim |author-last=Berners-Lee |author-link=Tim Berners-Lee |work=Frequently asked questions |title=Why the //, #, etc? |orig-year=2000 |date=2015 |publisher=[[World Wide Web Consortium]] |access-date=3 February 2010 |ref={{SfnRef|Berners-Lee|2000}}}}
* {{cite web |url=http://www.w3.org/html/wg/href/draft#url |title=Web addresses in HTML 5 |editor-first1=Daniel "Dan" |editor-last1=Connolly |editor-link1=Daniel Connolly (computer scientist) |editor-first2=C. Michael |editor-last2=Sperberg-McQueen |editor-link2=C. Michael Sperberg-McQueen |date=21 May 2009 |publisher=[[World Wide Web Consortium]] |access-date=13 September 2015 |ref={{SfnRef|W3C|2009}}}}
* {{cite web |url=http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html |archive-url=https://web.archive.org/web/20041208124351/http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html |archive-date=8 December 2004 |title=Completion of IANA Selection of IDNA Prefix |author=Internet Assigned Numbers Authority |work=IETF-Announce mailing list |date=14 February 2003 |access-date=3 September 2015 |ref={{SfnRef|IANA|2003}} |author-link=Internet Assigned Numbers Authority}}
* {{cite IETF |rfc=2396 |title=Uniform Resource Identifiers (URI): Generic Syntax |author-first1=Tim |author-last1=Berners-Lee |author-link1=Tim Berners-Lee |author-first2=Roy T. |author-last2=Fielding |author-link2=Roy T. Fielding |author-first3=Larry |author-last3=Masinter |author-link3=Larry Masinter |date=August 1998 |access-date=31 August 2015 |ref={{SfnRef|RFC 2396|1998}}}}
* {{cite IETF |rfc=7595 |title=Guidelines and Registration Procedures for URI Schemes |editor-first=Dave |editor-last=Thaler |author-first1=Tony |author-last1=Hansen |author-first2=Ted |author-last2=Hardie |date=June 2015 |ref={{SfnRef|IETF|2015}}}}
* {{cite IETF |rfc=3305 |title=Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations |editor-first1=Michael |editor-last1=Mealling |editor-link1=Michael Mealling |editor-first2=Ray |editor-last2=Denenberg |date=August 2002 |access-date=13 September 2015 |ref={{SfnRef|Joint W3C/IETF URI Planning Interest Group|2002}}}}
* {{cite IETF |rfc=3986 |title=Uniform Resource Identifiers (URI): Generic Syntax |author-first1=Tim |author-last1=Berners-Lee |author-link1=Tim Berners-Lee |author-first2=Roy T. |author-last2=Fielding |author-link2=Roy T. Fielding |author-first3=Larry |author-last3=Masinter |author-link3=Larry Masinter |date=January 2005 |access-date=31 August 2015 |ref={{SfnRef|RFC 3986|2005}}}}
* {{cite web |title=An Introduction to Multilingual Web Addresses |url=http://www.w3.org/International/articles/idn-and-iri/|date=9 May 2008 |access-date=11 January 2015 |ref={{SfnRef|W3C|2008}}}}
* {{cite web |title=What is Happening with "International URLs" |author-first=A. |author-last=Phillip |url=https://www.w3.org/International/wiki/IRIStatus |publisher=[[World Wide Web Consortium]] |date=2014 |access-date=11 January 2015 |ref={{SfnRef|W3C|2014}}}}
* {{cite web |last1=Lawrence |first1=Eric |title=Browser Arcana: IP Literals in URLs |url=https://docs.microsoft.com/en-us/archive/blogs/ieinternals/browser-arcana-ip-literals-in-urls |website=docs.microsoft.com |accessdate=22 June 2020 |archiveurl=https://web.archive.org/web/20200622181648/https://docs.microsoft.com/en-us/archive/blogs/ieinternals/browser-arcana-ip-literals-in-urls |archivedate=22 June 2020 |language=en-us}}
{{refend}}
==External links==
* [https://url.spec.whatwg.org/ URL specification] at [[WHATWG]]
* [https://www.ibm.com/support/knowledgecenter/en/SSGMCP_4.1.0/com.ibm.cics.ts.internet.doc/topics/dfhtl_uricomp.html The Components of a URL] from [[IBM]]
{{Hypermedia}}
{{Authority control}}
[[Category:URL| ]]
[[Category:Identifiers]]
[[Category:Computer-related introductions in 1994]]' |
Unified diff of changes made by edit ($1) (edit_diff) | '@@ -1,5 +1,5 @@
{{short description|Web address to a particular file or page}}
{{pp-semi-indef}}
-{{other uses}}
+{{other uses}}HARUNA ALKASIM MIKIYA
{{Use dmy dates|date=May 2020|cs1-dates=y}}
{{Infobox technology standard
@@ -11,5 +11,5 @@
| caption =
| status = Published
-| year_started =
+| year_started =2020
| version =[https://url.spec.whatwg.org Living Standard]
| version_date =2020
@@ -18,16 +18,11 @@
| organization = [[Internet Engineering Task Force]] (IETF)
| committee = [[Web Hypertext Application Technology Working Group]] (WHATWG)
-| base_standards =RFC 3986. – Uniform Resource Identifier (URI): Generic Syntax. <br/>
-RFC 4248. – The telnet URI Scheme. <br/>
-RFC 4266. – The gopher URI Scheme. <br/>
-RFC 6068. – The ‘mailto’ URI Scheme. <br/>
-RFC 6196. – Moving mailserver: URI Scheme to Historic. <br/>
-RFC 6270. – The ‘tn3270’ URI Scheme. <br/>
+| base_standards =Shi wankan tarwada ne kuma dogo
| related_standards =[[Uniform Resource Identifier|URI]], [[Uniform Resource Name|URN]]
-| abbreviation = URL
+| abbreviation = HARUNAALKASIMMIKIYA
| domain = [[World Wide Web]]
| license =[https://creativecommons.org/licenses/by/4.0/ CC BY 4.0]
-| website = https://url.spec.whatwg.org
-|first_published={{Start date and age|1994}}|authors=[[Tim Berners-Lee]]|series=Request for Comments (RFC)|editors=[[Anne van Kesteren]]}}
+| website = https://harunaalkasim mikiya.wikipedia.org
+|first_published={{Start date and age|1994}}|authors=[[ HARUNA ALKASIM ADAM ]]|series=Request for Comments (RFC)|editors=[[Anne van Kesteren]]}}
A '''Uniform Resource Locator''' ('''URL'''), colloquially termed a '''web address''',{{sfnp|W3C|2009}} is a reference to a [[web resource]] that specifies its location on a [[computer network]] and a mechanism for retrieving it. A URL is a specific type of [[Uniform Resource Identifier]] (URI),<ref>{{Cite web |url=https://zzz.buzz/2017/09/19/forward-and-backslashes-in-urls/ |title=Forward and Backslashes in URLs |website=zzz.buzz |language=en |access-date=19 September 2018}}</ref>{{sfnp|RFC 3986|2005}} although many people use the two terms interchangeably.{{sfnp|Joint W3C/IETF URI Planning Interest Group|2002}}{{efn|A URL implies the means to access an indicated resource and is denoted by a protocol or an access mechanism, which is not true of every URI.{{sfnp|RFC 2396|1998}}{{sfnp|Joint W3C/IETF URI Planning Interest Group|2002}} Thus <code><nowiki>http:</nowiki>//www.example.com</code> is a URL, while <code>www.example.com</code> is not.<ref>{{Cite web |url=https://danielmiessler.com/study/url-uri/#gs.Hs64zOs |title=The Difference Between URLs and URIs |author-last=Miessler |author-first=Daniel}}</ref>}} URLs occur most commonly to reference [[web page]]s ([[http]]), but are also used for file transfer ([[File Transfer Protocol|ftp]]), email ([[mailto]]), database access ([[Java Database Connectivity|JDBC]]), and many other applications.
' |
New page size ($1) (new_size) | 14134 |
Old page size ($1) (old_size) | 14358 |
Size change in edit ($1) (edit_delta) | -224 |
Lines added in edit ($1) (added_lines) | [
0 => '{{other uses}}HARUNA ALKASIM MIKIYA',
1 => '| year_started =2020 ',
2 => '| base_standards =Shi wankan tarwada ne kuma dogo',
3 => '| abbreviation = HARUNAALKASIMMIKIYA',
4 => '| website = https://harunaalkasim mikiya.wikipedia.org',
5 => '|first_published={{Start date and age|1994}}|authors=[[ HARUNA ALKASIM ADAM ]]|series=Request for Comments (RFC)|editors=[[Anne van Kesteren]]}}'
] |
Lines removed in edit ($1) (removed_lines) | [
0 => '{{other uses}}',
1 => '| year_started = ',
2 => '| base_standards =RFC 3986. – Uniform Resource Identifier (URI): Generic Syntax. <br/>',
3 => 'RFC 4248. – The telnet URI Scheme. <br/>',
4 => 'RFC 4266. – The gopher URI Scheme. <br/>',
5 => 'RFC 6068. – The ‘mailto’ URI Scheme. <br/>',
6 => 'RFC 6196. – Moving mailserver: URI Scheme to Historic. <br/>',
7 => 'RFC 6270. – The ‘tn3270’ URI Scheme. <br/>',
8 => '| abbreviation = URL',
9 => '| website = https://url.spec.whatwg.org',
10 => '|first_published={{Start date and age|1994}}|authors=[[Tim Berners-Lee]]|series=Request for Comments (RFC)|editors=[[Anne van Kesteren]]}}'
] |
All external links added in the edit ($1) (added_links) | [
0 => 'https://harunaalkasim'
] |
All external links in the new text ($1) (all_links) | [
0 => 'https://tools.ietf.org/html/rfc2717',
1 => 'https://tools.ietf.org/html/rfc7595',
2 => 'https://tools.ietf.org/html/rfc1866',
3 => 'https://tools.ietf.org/html/rfc2854',
4 => 'https://zzz.buzz/2017/09/19/forward-and-backslashes-in-urls/',
5 => 'https://danielmiessler.com/study/url-uri/#gs.Hs64zOs',
6 => 'https://www.ucc.ie/archive/curia/dtds/html-spec.ps',
7 => 'http://ds.internic.net/internet-drafts/draft-ietf-uri-url-08.txt',
8 => 'https://listserv.heanet.ie/cgi-bin/wa?A2=ind9501&L=HTML-WG&P=R23201&X=C6F9505B05BC9A3B67',
9 => 'https://books.google.com/?id=6u2sBAAAQBAJ&pg=PA193',
10 => 'https://books.google.com/?id=DW0uyBZzEDwC&pg=PT124',
11 => 'https://www.wikidata.org/wiki/Q42253#identifiers',
12 => 'https://url.spec.whatwg.org',
13 => 'https://creativecommons.org/licenses/by/4.0/',
14 => 'https://tools.ietf.org/html/rfc1738',
15 => 'https://tools.ietf.org/html/rfc1630',
16 => 'http://news.bbc.co.uk/1/hi/technology/8306631.stm',
17 => 'http://www.w3.org/Conferences/IETF92/WWX_BOF_mins.html',
18 => 'http://www.w3.org/Addressing/URL/url-spec.txt',
19 => '//doi.org/10.17487%2FRFC1738',
20 => 'http://www.w3.org/People/Berners-Lee/FAQ.html#etc',
21 => 'http://www.w3.org/html/wg/href/draft#url',
22 => 'https://web.archive.org/web/20041208124351/http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html',
23 => 'http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html',
24 => 'https://tools.ietf.org/html/rfc2396',
25 => '//doi.org/10.17487%2FRFC2396',
26 => '//doi.org/10.17487%2FRFC7595',
27 => 'https://tools.ietf.org/html/rfc3305',
28 => '//doi.org/10.17487%2FRFC3305',
29 => 'https://tools.ietf.org/html/rfc3986',
30 => '//doi.org/10.17487%2FRFC3986',
31 => 'http://www.w3.org/International/articles/idn-and-iri/',
32 => 'https://www.w3.org/International/wiki/IRIStatus',
33 => 'https://web.archive.org/web/20200622181648/https://docs.microsoft.com/en-us/archive/blogs/ieinternals/browser-arcana-ip-literals-in-urls',
34 => 'https://docs.microsoft.com/en-us/archive/blogs/ieinternals/browser-arcana-ip-literals-in-urls',
35 => 'https://url.spec.whatwg.org/',
36 => 'https://www.ibm.com/support/knowledgecenter/en/SSGMCP_4.1.0/com.ibm.cics.ts.internet.doc/topics/dfhtl_uricomp.html',
37 => 'https://d-nb.info/gnd/4753514-3',
38 => 'https://harunaalkasim'
] |
Links in the page, before the edit ($1) (old_links) | [
0 => '//doi.org/10.17487%2FRFC1738',
1 => '//doi.org/10.17487%2FRFC1738',
2 => '//doi.org/10.17487%2FRFC2396',
3 => '//doi.org/10.17487%2FRFC2396',
4 => '//doi.org/10.17487%2FRFC3305',
5 => '//doi.org/10.17487%2FRFC3305',
6 => '//doi.org/10.17487%2FRFC3986',
7 => '//doi.org/10.17487%2FRFC3986',
8 => '//doi.org/10.17487%2FRFC7595',
9 => '//doi.org/10.17487%2FRFC7595',
10 => 'http://ds.internic.net/internet-drafts/draft-ietf-uri-url-08.txt',
11 => 'http://news.bbc.co.uk/1/hi/technology/8306631.stm',
12 => 'http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html',
13 => 'http://www.w3.org/Addressing/URL/url-spec.txt',
14 => 'http://www.w3.org/Conferences/IETF92/WWX_BOF_mins.html',
15 => 'http://www.w3.org/International/articles/idn-and-iri/',
16 => 'http://www.w3.org/People/Berners-Lee/FAQ.html#etc',
17 => 'http://www.w3.org/html/wg/href/draft#url',
18 => 'https://books.google.com/?id=6u2sBAAAQBAJ&pg=PA193',
19 => 'https://books.google.com/?id=DW0uyBZzEDwC&pg=PT124',
20 => 'https://creativecommons.org/licenses/by/4.0/',
21 => 'https://d-nb.info/gnd/4753514-3',
22 => 'https://danielmiessler.com/study/url-uri/#gs.Hs64zOs',
23 => 'https://docs.microsoft.com/en-us/archive/blogs/ieinternals/browser-arcana-ip-literals-in-urls',
24 => 'https://listserv.heanet.ie/cgi-bin/wa?A2=ind9501&L=HTML-WG&P=R23201&X=C6F9505B05BC9A3B67',
25 => 'https://tools.ietf.org/html/rfc1630',
26 => 'https://tools.ietf.org/html/rfc1738',
27 => 'https://tools.ietf.org/html/rfc1866',
28 => 'https://tools.ietf.org/html/rfc2396',
29 => 'https://tools.ietf.org/html/rfc2717',
30 => 'https://tools.ietf.org/html/rfc2854',
31 => 'https://tools.ietf.org/html/rfc3305',
32 => 'https://tools.ietf.org/html/rfc3986',
33 => 'https://tools.ietf.org/html/rfc7595',
34 => 'https://url.spec.whatwg.org',
35 => 'https://url.spec.whatwg.org/',
36 => 'https://web.archive.org/web/20041208124351/http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html',
37 => 'https://web.archive.org/web/20200622181648/https://docs.microsoft.com/en-us/archive/blogs/ieinternals/browser-arcana-ip-literals-in-urls',
38 => 'https://www.ibm.com/support/knowledgecenter/en/SSGMCP_4.1.0/com.ibm.cics.ts.internet.doc/topics/dfhtl_uricomp.html',
39 => 'https://www.ucc.ie/archive/curia/dtds/html-spec.ps',
40 => 'https://www.w3.org/International/wiki/IRIStatus',
41 => 'https://www.wikidata.org/wiki/Q42253#identifiers',
42 => 'https://zzz.buzz/2017/09/19/forward-and-backslashes-in-urls/'
] |
Whether or not the change was made through a Tor exit node ($1) (tor_exit_node) | false |
Unix timestamp of change ($1) (timestamp) | 1609421021 |
