Photo:1
Photo:2
Photo:3
Photo:4
Photo:1 Photo:2 Photo:3 Photo:4 |
| History | |
| 2>
The Uniform Resource Locator was created in 1994[2] by Tim Berners-Lee and the URI working group of the Internet Engineering Task Force (IETF) as an outcome of collaboration started at the IETF Living Documents "Birds of a Feather" session in 1992.[3][4] The format combines the pre-existing system of domain names (created in 1985) with file path syntax, where forward slashes are used to separate folder and file names. Conventions already existed where server names could be prepended to complete file paths, preceded by a double-slash (//).[5]
[edit] Tags:Uri,Edit,Tim Berners-lee,Internet Engineering Task Force,Birds Of A Feather,Domain Names,File Path,Forward Slashes,Folder,File,Domain Name,Resource,Internet,Uniform Resource Locator,Path,Read, | |
| Syntax | |
| 2>
Main article: URI scheme#Generic syntax
Every URL consists of some of the following: the scheme name (commonly called protocol), followed by a colon, two slashes,[note 1] then, depending on scheme, a domain name[note 2] (alternatively, IP address), a port number, the path of the resource to be fetched or the program to be run, then, for programs such as Common Gateway Interface (CGI) scripts, a query string,[7][8] and an optional fragment identifier.[9]
The syntax is:-
scheme://domain:port/path?query_string#fragment_id
The scheme name defines the namespace, purpose, and the syntax of the remaining part of the URL. Software will try to process a URL according to its scheme and context. For example, a web browser will usually dereference the URL http://example.org:80 by performing an HTTP request to the host at example.org, using port number 80. The URL mailto:bob@example.com may start an e-mail composer with the address bob@example.com in the To field.
Other examples of scheme names include https:, gopher:, wais:, ftp:. URLs with https as a scheme (such as https://example.com/) require that requests and responses will be made over a secure connection to the website. Some schemes that require authentication allow a username, and perhaps a password too, to be embedded in the URL, for example ftp://asmith@ftp.example.org. Passwords embedded in this way are not conducive to secure working, but the full possible syntax is
scheme://username:password@domain:port/path?query_string#fragment_id
The domain name or IP address gives the destination location for the URL. The domain google.com, or its IP address 72.14.207.99, is the address of Google's website.
The domain name portion of a URL is not case sensitive since DNS ignores case: http://en.example.org/ and HTTP://EN.EXAMPLE.ORG/ both open the same page.
The port number is optional; if omitted, the default for the scheme is used. For example, http://vnc.example.com:5800 connects to port 5800 of vnc.example.com, which may be appropriate for a VNC remote control session. If the port number is omitted for an http: URL, the browser will connect on port 80, the default HTTP port. The default port for an https: request is 443.
The path is used to specify and perhaps find the resource requested. It is case-sensitive, though it may be treated as case-insensitive by some servers, especially those based on Microsoft Windows. If the server is case sensitive and http://en.example.org/wiki/URL is correct, http://en.example.org/WIKI/URL or http://en.example.org/wiki/url will display an HTTP 404 error page, unless these URLs point to valid resources themselves.
The query string contains data to be passed to software running on the server. It may contain name/value pairs separated by ampersands, for example ?first_name=John&last_name=Doe.
The fragment identifier, if present, specifies a part or a position within the overall resource or document. When used with HTTP, it usually specifies a section or location within the page, and the browser may scroll to display that part of the page.
[edit] Tags:Scheme Name,Ip Address,Port Number,Common Gateway Interface,Scripts,Query String,Fragment Identifier,Web Browser,Http,E-mail,Https,Gopher,Wais,Software Running On The Server,Uri Scheme,Website,Article, | |
| Absolute and relative URLs | |
| 2>
According to RFC 1738, which defined URLs in 1994, when resources contain references to other resources, they can use relative links to define the location of the second resource as if to say, "in the same place as this one except with the following relative path". It went on to say that such relative URLs are dependent on the original URL containing a hierarchical structure against which the relative link is based, and that the ftp, http, and file URL schemes are examples of some that can be considered hierarchical, with the components of the hierarchy being separated by "/".[10]
[edit] Tags: | |
| URLs as locators | |
| 2>
A URL is a URI that, "in addition to identifying a resource, provides a means of locating the resource by describing its primary access mechanism (e.g., its network location)".[11][12]
[edit] Tags: | |
| Internet hostnames | |
| 2>
Main article: Hostname
On the Internet, a hostname is a domain name assigned to a host computer. This is usually a combination of the host's local name with its parent domain's name. For example, en.example.org consists of a local hostname (en) and the domain name example.org. The hostname is translated into an IP address via the local hosts file, or the domain name system (DNS) resolver. It is possible for a single host computer to have several hostnames; but generally the operating system of the host prefers to have one hostname that the host uses for itself.
Any domain name can also be a hostname, as long as the restrictions mentioned below are followed. For example, both "en.example.org" and "example.org" can be hostnames if they both have IP addresses assigned to them. The domain name "xyz.example.org" may not be a hostname if it does not have an IP address, but "aa.xyz.example.org" may still be a hostname. All hostnames are domain names, but not all domain names are hostnames.
[edit] Tags:Hostname,Hosts File,Domain Name System,Operating System,Ip Addresses, | |
| See also | |
| 2>
CURIE (Compact URI)
Extensible Resource Identifier (XRI)
Fragment identifier
Internationalized Resource Identifier (IRI)
URL normalization
[edit] Tags:Curie,Extensible Resource Identifier,Internationalized Resource Identifier, | |
| Notes | |
| 2>
^ Berners-Lee has said that, given the colon following the URI scheme, the two forward slashes before the domain name were unnecessary.[6]
^ Berners-Lee also later regretted the use of dots to separate the parts of the domain name, wishing he had used slashes throughout. For example, http://www.example.com/path/to/name would have been written http:com/example/www/path/to/name[5]
[edit] Tags: | |
| References | |
| 2>
^ RFC 3305 "URI Partitioning: There is some confusion in the web community over the partitioning of URI space, specifically, the relationship among the concepts of URL, URN, and URI. The confusion owes to the incompatibility between two different views of URI partitioning, which we call the 'classical' and 'contemporary' views."
^ RFC 1738 Uniform Resource Locators (URL). This RFC is now obsolete. It has been superseded by a newer RFC (see the RFC Index)
^ "Living Documents BoF Minutes". W3.org. http://www.w3.org/Conferences/IETF92/WWX_BOF_mins.html. Retrieved 2011-12-26.
^ "URL Specification". http://www.w3.org/Addressing/URL/url-spec.txt. Retrieved 2011-12-26.
^ a b Berners-Lee, Tim. "Frequently asked questions by the press". http://www.w3.org/People/Berners-Lee/FAQ#etc. Retrieved 2010-02-03.
^ "Technology | Berners-Lee 'sorry' for slashes". BBC News. 2009-10-14. http://news.bbc.co.uk/1/hi/technology/8306631.stm. Retrieved 2010-02-14.
^ RFC 1738
^ "PHP parse_url() Function". http://us.php.net/parse_url. Retrieved 2009-03-12.
^ "URL Syntax". Pangea.stanford.edu. 2004-07-20. http://pangea.stanford.edu/computerinfo/hosting/urlsyntax/index.html. Retrieved 2011-12-26.
^ Berners-Lee, Tim; et al (December 1994). "Uniform Resource Locators (URL)". IETF. http://www.faqs.org/rfcs/rfc1738.html. Retrieved 20 November 2010. "Hierarchical schemes and relative links. In some cases, URLs are used to locate resources that contain pointers to other resources. In some cases, those pointers are represented as relative links where the expression of the location of the second resource is in terms of "in the same place as this one except with the following relative path". Relative links are not described in this document. However, the use of relative links depends on the original URL containing a hierarchical structure against which the relative link is based. Some URL schemes (such as the ftp, http, and file schemes) contain names that can be considered hierarchical; the components of the hierarchy are separated by "/"."
^ Tim Berners-Lee, Roy T. Fielding, Larry Masinter. (January 2005). “Uniform Resource Identifier (URI): Generic Syntax”. Internet Society. RFC 3986; STD 66.
^ By describing its primary access mechanism
[edit] Tags:Urn,Uniform Resource Identifier, | |
| External links | |
| 2>
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax (ASCII version)
v
d
e
Hypermedia
Basics
Hypertext
Hyperlink
Hypervideo
Adaptive hypermedia
educational
authoring
Hyperlinks in virtual worlds
Resource identifiers
Uniform Resource Identifier
Internationalized Resource Identifier
Dereferenceable Uniform Resource Identifier
Uniform Resource Name
Uniform Resource Locator
Extensible Resource Identifier
Persistent Uniform Resource Locator
Semantic URL
Concepts
URI scheme
URL normalization
URL redirection
XML namespace
Hostname
Domain name
Fragment identifier
Website
Webpage
Path
Hypertext
Inline linking
image map
Internal link
Object hyperlinking
Copyright aspects of hyperlinking and framing
anchor text
inbound link/backlink
deep linking
Methods of website linking
link farm
linkback
Dead link
HTTP referrer
Fat link
Link inventory
Organic linking
click path
click here
Typed link
transclusion
Screen hotspot
Source tracking
Link rot
Internet bookmark
Technology
CURIE
Hypertext Transfer Protocol
XLink
See also
Interactive novel
Interactive fiction
Hypertext poetry
Timeline
Copyright aspects of hyperlinking and framing
World Wide Web
Retrieved from "http://en.wikipedia.org/w/index.php?title=Uniform_resource_locator&oldid=475551244"
Categories: Uniform resource locatorIdentifiersHidden categories: Articles needing cleanup from December 2010All articles needing cleanupCleanup tagged articles without a reason fieldUse dmy dates from May 2011
Personal tools
Log in / create account
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
Actions
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact Wikipedia
Toolbox
What links here
Related changes
Upload file
Special pages
Permanent link
Cite this page
Print/export
Create a bookDownload as PDFPrintable version
Languages
Afrikaans
Alemannisch
العربية
Azərbaycanca
Беларуская (тарашкевіца)
Български
Català
Чӑвашла
Česky
Cymraeg
Dansk
Deutsch
Eesti
Ελληνικά
Español
Esperanto
Euskara
فارسی
Français
Gaeilge
Galego
ગુજરાતી
한국어
हिन्दी
Hrvatski
Bahasa Indonesia
Interlingua
Íslenska
Italiano
עברית
Basa Jawa
ಕನ್ನಡ
Қазақша
Latviešu
Lëtzebuergesch
Magyar
Bahasa Melayu
Nederlands
日本語
Norsk (bokmål)
Norsk (nynorsk)
Олык Марий
ភាសាខ្មែរ
Polski
Português
Română
Русский
Simple English
Slovenčina
Slovenščina
Српски / Srpski
Svenska
தமிழ்
తెలుగు
ไทย
Тоҷикӣ
Türkçe
Українська
اردو
Tiếng Việt
Yorùbá
粵語
中文
This page was last modified on 7 February 2012 at 10:06.
Text is available under the Creative Commons Attribution-ShareAlike License;
additional terms may apply.
See Terms of use for details.
Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.Contact us
Privacy policy
About Wikipedia
Disclaimers
Mobile view
if ( window.isMSIE55 ) fixalpha();
if ( window.mediaWiki ) {
mw.loader.load(["mediawiki.user", "mediawiki.util", "mediawiki.page.ready", "mediawiki.legacy.wikibits", "mediawiki.legacy.ajax", "mediawiki.legacy.mwsuggest", "ext.gadget.wmfFR2011Style", "ext.vector.collapsibleNav", "ext.vector.collapsibleTabs", "ext.vector.editWarning", "ext.vector.simpleSearch", "ext.UserBuckets", "ext.articleFeedback.startup", "ext.articleFeedbackv5.startup", "ext.markAsHelpful"]);
}
if ( window.mediaWiki ) {
mw.user.options.set({"ccmeonemails":0,"cols":80,"date":"default","diffonly":0,"disablemail":0,"disablesuggest":0,"editfont":"default","editondblclick":0,"editsection":1,"editsectiononrightclick":0,"enotifminoredits":0,"enotifrevealaddr":0,"enotifusertalkpages":1,"enotifwatchlistpages":0,"extendwatchlist":0,"externaldiff":0,"externaleditor":0,"fancysig":0,"forceeditsummary":0,"gender":"unknown","hideminor":0,"hidepatrolled":0,"highlightbroken":1,"imagesize":2,"justify":0,"math":1,"minordefault":0,"newpageshidepatrolled":0,"nocache":0,"noconvertlink":0,"norollbackdiff":0,"numberheadings":0,"previewonfirst":0,"previewontop":1,"quickbar":5,"rcdays":7,"rclimit":50,"rememberpassword":0,"rows":25,"searchlimit":20,"showhiddencats":false,"showjumplinks":1,"shownumberswatching":1,"showtoc":1,"showtoolbar":1,"skin":"vector","stubthreshold":0,"thumbsize":4,"underline":2,"uselivepreview":0,"usenewrc":0,"watchcreations":1,"watchdefault":0,"watchdeletion":0,"watchlistdays":3,"watchlisthideanons":0,
"watchlisthidebots":0,"watchlisthideliu":0,"watchlisthideminor":0,"watchlisthideown":0,"watchlisthidepatrolled":0,"watchmoves":0,"wllimit":250,"flaggedrevssimpleui":1,"flaggedrevsstable":0,"flaggedrevseditdiffs":true,"flaggedrevsviewdiffs":false,"vector-simplesearch":1,"useeditwarning":1,"vector-collapsiblenav":1,"usebetatoolbar":1,"usebetatoolbar-cgd":1,"wikilove-enabled":1,"variant":"en","language":"en","searchNs0":true,"searchNs1":false,"searchNs2":false,"searchNs3":false,"searchNs4":false,"searchNs5":false,"searchNs6":false,"searchNs7":false,"searchNs8":false,"searchNs9":false,"searchNs10":false,"searchNs11":false,"searchNs12":false,"searchNs13":false,"searchNs14":false,"searchNs15":false,"searchNs100":false,"searchNs101":false,"searchNs108":false,"searchNs109":false,"gadget-wmfFR2011Style":1});;mw.user.tokens.set({"editToken":"+\\","watchToken":false});;mw.loader.state({"user.options":"ready","user.tokens":"ready"});
/* cache key: enwiki:resourceloader:filter:minify-js:4:b41a86ec4e0fe8329bc3ce917e792339 */
}
Tags:Cleanup,Hypermedia,Hypertext,Hyperlink,Hypervideo,Adaptive Hypermedia,Educational,Authoring,Hyperlinks In Virtual Worlds,Dereferenceable Uniform Resource Identifier,Uniform Resource Name,Persistent Uniform Resource Locator,Xml Namespace,Webpage,Inline Linking,Image Map,Internal Link,Object Hyperlinking,Copyright Aspects Of Hyperlinking And Framing,Anchor Text,Inbound Link,Backlink,Deep Linking,Methods Of Website Linking,Link Farm,Linkback,Dead Link,Http Referrer,Fat Link,Link Inventory,Organic Linking,Click Path,Click Here,Typed Link,Transclusion,Screen Hotspot,Source Tracking,Link Rot, | |
zote monety |