URL Full Form

What is the full form of URL?

The full form of the URL is “Uniform Resource Locator.” A URL is a link address on the Internet.URLs are used to access and retrieve these resources through a web browser or other internet-enabled application. URLs were introduced in 1994 by Tim Berners-Lee and the Working Group on Internet Engineering. A URL is an address or string used to search for Internet data. A URL is in the form of a Uniform Resource Identifier (URI).

Background

The URL was developed by Tim Berners-Lee, inventor of the World Wide Web, and his URI Working Group of his Internet Engineering Task Force (IETF) in the IETF Living Documents Birds of the 1992 Feather Session.

This format combines the existing system of domain names (created in 1985) with file path syntax that uses forward slashes to separate directories and file names. A convention already existed that allowed the server name to be prepended to the full file path with a double slash (//).

Berners-Lee later expressed regret for using periods to separate domain name parts in URIs, and given the colon after the first component of a URI, his two No slash was needed. An early (1993) draft of the HTML specification [11] mentioned a "universal" resource locator. This was removed between June 1994 (RFC 1630) and October 1994 (draft-ietf-uri-url-08.txt).

Information contained in the URL

The URL contains the following details shown below

• Protocol name:

Colon with a double slash:

(//)

• Hostname (domain name) or IP address

• A colon followed by a port number

• File path

Example of URL

Complete ATM form

to the above URL

• Protocol - HTTP

• Domain - ABC.com

• resource path - /complete form

You can manually enter the URL by typing it into your web browser's address bar. If the URL does not contain a valid domain, the browser may display a server not found error, and if the URL has an incorrect root, the browser may display a 404 error. The URL does not contain spaces and uses forward slashes to reflect different files. Hyphens and underscores are used.

URL syntax:

Protocol:

//hostname/filename

protocol:

A protocol is a set of standard rules used to allow electronic devices to communicate with each other.

hostname:

Write the name of the server on your network.

file name:

Describes the pathname to the file on the server.

URL https://example.com/php-function contains info logs.

HTTPS, hostname:

example.com and filename:

PHP function.

What is a URI?

URI stands for Uniform Resource Identifier. A generic term for all names and addresses that refer to objects on the World Wide Web. Generally, it is a string that identifies the name and location of a logical resource or file or resource in a consistent format.

There are two types of URIs:

These are known as uniform resource locators (URLs) and uniform resource names (URNs). This allows access to resources from other computers over a network or the World Wide Web.

Basic URL structure:

You can type any of the above URLs into your browser's address bar and tell it to load the associated page (resource).

There are different parts to a URL, some of which are mandatory and others of which are optional. The following sections provide details on the most important parts of the URL below:

Note 1:

A URL can be thought of as a regular street address:

The scheme represents the postal service to use, the domain name is the city or town, and the port is like a postal code. A path represents a building where mail is delivered. Parameters represent additional information, such as the number of apartments within the building. Finally, the anchor means the actual person to whom the email was addressed.

Note 2 :

There are some extra parts and extra rules related to URLs, but they are irrelevant to normal users and web developers. No need to worry about them. You don't need to know them to create and use fully functional URLs.

Scheme

The first part of the URL is a scheme that specifies the protocol that browsers should use to request the resource (a protocol is a specified method for exchanging or transmitting data over a computer network). The website protocol is usually HTTPS or HTTP (the non-secure version). Web page addressing requires one of two things, but browsers also know how to handle other schemes such as mailto.

(to open your email client) so don't be surprised if you see other logs.

Authority

The following are the privileges separated from the schema by character pattern.//. If present, the authority contains both the domain (e.g. www.example.com) and the port (80) separated by a colon.

• Domain indicates the requested web server. Usually, this is a domain name, but an IP address can also be used (although this is less practical as it is rare).

• Ports specify the technical “gates” for accessing web server resources. Usually omitted if the web server allows access to that resource using the standard HTTP protocol port (80 for HTTP, 443 for HTTPS). otherwise required.

Note:

The delimiter between scheme and authority is:

The //.colon separates the scheme from the next part of the URL, and // indicates that the next part of the URL is the authority.

An example of a URL without permissions is an email client (mailto: Hoover). It contains the schema but does not use the permissions component. There are no double slashes after the colon, they only act as a separator between the scheme and the email address.

Path to resource

The path to myfile.html on your web server is /path/to/myfile.html. In the early days of the web, such paths represented physical file locations on the web server, but today most abstractions are managed by web servers that have no physical reality.

Parameter

The web server receives additional parameters key1=value1 and key2=value2. These parameters are a list of key-value pairs separated by & symbols. The web server can use these parameters to do additional processing before returning the resource. Every web server has its own set of rules regarding parameters, and the only sure way to know if a particular web server handles parameters is to ask the web server owner.

Anchor

#SomewhereInTheDocument points to another portion of the resource. Anchors represent a kind of "bookmark" within a resource and provide instructions for the browser to display the content at that "bookmarked" location. For example, in an HTML document the browser scrolls to the point where the anchor is defined. In a video or audio document, the browser will attempt to move to the time represented by the anchor. Note that the part after #, also called fragment identifier, is not sent to the server with the request.

How to use URLs

You can type any URL directly into your browser's address bar to navigate to the resource behind it. But you have to understand something that this whole thing is a piece of the iceberg.

The HTML language (discussed later) makes extensive use of URLs.

• Create links to other documents using the element.

• Link documents to related resources using various elements such as <link>. or [remove];

• Display media such as images (<img> )

Absolute and Relative URLs

The above are what are called absolute URLs, but there are also what are called relative URLs. The URL standard defines both but uses the terms absolute and relative URL strings to distinguish them from URL objects (in-memory representations of URLs).

Let's explore what the difference between absolute and relative means in the context of URLs.

The required parts of the URL are highly dependent on the context in which the URL is used. URLs have no context in the browser's address bar, so you must specify full (or absolute) URLs like the one above. You do not need to specify the protocol (browsers use HTTP by default) or the port (needed only if the target web server uses an uncommon port), but all other parts of the URL are required. When URLs are used within the document.

The situation is slightly different with HTML pages. Since the browser already has its URL for the document, it can use that information to fill in the missing parts of the URL available for that document. You can distinguish between absolute and relative URLs simply by looking at the path portion of the URL. If the path portion of the URL begins with a '/' character, the browser fetches that resource from the server's top-level root directory without referring to the context specified in the current document.