{"id":1678,"date":"2022-03-07T15:58:01","date_gmt":"2022-03-07T19:58:01","guid":{"rendered":"https:\/\/ten30media.com\/sapnew\/?p=1678"},"modified":"2022-03-07T16:17:48","modified_gmt":"2022-03-07T20:17:48","slug":"url-explained","status":"publish","type":"post","link":"https:\/\/ten30media.com\/sapnew\/url-explained\/","title":{"rendered":"URL Explained"},"content":{"rendered":"

URL Explained<\/strong><\/p>\n

\"URL

URL stands for Uniform Resource Locator<\/p><\/div>\n

This article discusses Uniform Resource Locators (URLs), explaining what they are and how they’re structured.<\/p>\n

Summary<\/strong><\/a><\/p>\n

With\u00a0Hypertext\u00a0and\u00a0HTTP,\u00a0URL<\/em><\/strong>\u00a0is one of the key concepts of the Web. It is the mechanism used by\u00a0browsers\u00a0to retrieve any published resource on the web.<\/p>\n

URL<\/strong>\u00a0stands for\u00a0Uniform Resource Locator<\/em>. A URL is nothing more than the address of a given unique resource on the Web. In theory, each valid URL points to a unique resource. Such resources can be an HTML page, a CSS document, an image, etc. In practice, there are some exceptions, the most common being a URL pointing to a resource that no longer exists or that has moved. As the resource represented by the URL and the URL itself are handled by the Web server, it is up to the owner of the web server to carefully manage that resource and its associated URL.<\/p>\n

Basics: anatomy of a URL<\/strong><\/p>\n

Here are some examples of URLs:<\/p>\n

https:\/\/developer.mozilla.org<\/p>\n

https:\/\/developer.mozilla.org\/en-US\/docs\/Learn\/<\/p>\n

https:\/\/developer.mozilla.org\/en-US\/search?q=URL<\/p>\n

Any of those URLs can be typed into your browser’s address bar to tell it to load the associated page (resource).<\/p>\n

A URL is composed of different parts, some mandatory and others optional. The most important parts are highlighted on the URL below (details are provided in the following sections):<\/p>\n

\"\"<\/p>\n

Note:<\/strong>\u00a0You might think of a URL like a regular postal mail address: the\u00a0scheme<\/em>\u00a0represents the postal service you want to use, the\u00a0domain name<\/em>\u00a0is the city or town, and the\u00a0port<\/em>\u00a0is like the zip code; the\u00a0path<\/em>\u00a0represents the building where your mail should be delivered; the\u00a0parameters<\/em>\u00a0represent extra information such as the number of the apartment in the building; and, finally, the\u00a0anchor<\/em>\u00a0represents the actual person to whom you’ve addressed your mail.<\/p>\n

Note:<\/strong>\u00a0There are\u00a0some extra parts and some extra rules\u00a0regarding URLs, but they are not relevant for regular users or Web developers. Don’t worry about this, you don’t need to know them to build and use fully functional URLs.<\/p>\n

Scheme<\/strong><\/p>\n

\"\"<\/p>\n

The first part of the URL is the\u00a0scheme<\/em>, which indicates the protocol that the browser must use to request the resource (a protocol is a set method for exchanging or transferring data around a computer network). Usually for websites the protocol is HTTPS or HTTP (its unsecured version). Addressing web pages requires one of these two, but browsers also know how to handle other schemes such as\u00a0mailto:\u00a0(to open a mail client), so don’t be surprised if you see other protocols.<\/p>\n

Authority<\/strong><\/p>\n

\"\"<\/p>\n

Next follows the\u00a0authority<\/em>, which is separated from the scheme by the character pattern\u00a0:\/\/. If present the authority includes both the\u00a0domain<\/em>\u00a0(e.g.,\u00a0www.example.com) and the\u00a0port<\/em>\u00a0(80), separated by a colon:<\/p>\n