A PROTOCOL EVERY WEB MAPPER MUST KNOW- HTTPs
HTTP stands for Hypertext Transfer Protocol. It's a stateless, application layer protocol for communicating between distributed systems, and is the foundation of the modern web. As a web developer/Mapper, we all must have a strong understanding of this protocol.
HTTP allows for communication between a variety of hosts and clients and also supports a mixture of network configurations through the internet. it does not keep state between different message exchanges hence making itself a stateless protocol. The communication usually takes place over TCP/IP , but any reliable transport can be used. The default port for TCP/IP is 80, but other ports can also be used. The client sends a request to the server (host) and receives response just on his/her browser.
The current version of the protocol is HTTP/1.1, which adds a few extra features to the previous 1.0 version. The most important of these, in my opinion, includes persistent connections, chunked transfer-coding and fine-grained caching headers.
URLs
The full meaning of a URL is a Uniform Resource Locator. This acts as a path through which a message request is sent by the user. The components of a url includes:
1.Protocol- this is the http as discussed above.
2.Domain- it is the IP address
3.Port- consists of some numbers
4.Resource Path- The directory to which a certain resource is located and
5.Query- might consist of the user requests
http can also be HTTPS for Secure communications in the internet.
HTTP Request Verbs
HTTP allows for communication between a variety of hosts and clients and also supports a mixture of network configurations through the internet. it does not keep state between different message exchanges hence making itself a stateless protocol. The communication usually takes place over TCP/IP , but any reliable transport can be used. The default port for TCP/IP is 80, but other ports can also be used. The client sends a request to the server (host) and receives response just on his/her browser.
The current version of the protocol is HTTP/1.1, which adds a few extra features to the previous 1.0 version. The most important of these, in my opinion, includes persistent connections, chunked transfer-coding and fine-grained caching headers.
URLs
The full meaning of a URL is a Uniform Resource Locator. This acts as a path through which a message request is sent by the user. The components of a url includes:
1.Protocol- this is the http as discussed above.
2.Domain- it is the IP address
3.Port- consists of some numbers
4.Resource Path- The directory to which a certain resource is located and
5.Query- might consist of the user requests
http can also be HTTPS for Secure communications in the internet.
HTTP Request Verbs
- GET-Fetches an existing resource.
- POST-Creates a new resource
- PUT- updates an existing Resource
- DELETE- Deletes an existing resource.
- HEAD: this is similar to GET , but without the message body . It's used to retrieve the server headers for a particular resource, generally to check if the resource has changed, via timestamps.
- TRACE: used to retrieve the hops that a request takes to round trip from the server . Each intermediate proxy or gateway would inject its IP or DNS name into the Via header field. This can be used for diagnostic purposes.
- OPTIONS: used to retrieve the server capabilities. On the clientside, it can be
used to modify the request based on what the server can support.
Comments