Hypertext is structured text that uses logical links (called hyperlinks) between nodes that contain text.HTTP is the protocol for exchanging or transferring hypertext.
HTTP is responsible for processing and responding to requests to view a web page.It also serves to send additional information such as sending forms with messages, etc.
After the transaction is finished, HTTP does not save any information about it, therefore it is considered a "stateless" protocol.To save the information between different requests , webmasters often use cookies or parameter steps.
The HTTP protocol generally uses port 80.
HTTP is based on the client-server model, where an HTTP client (a browser for example) opens a connection and make a sun The server responds to the request with a resource (text, graphics, etc.) or an error message, and finally the connection is closed.One of the most famous HTTP error messages is 404 Not found (not found).
The development of HTTP initiated by Tim Berners-Lee at CERN in 1989.The development of HTTP standards was coordinated by the Internet Engineering Task Force (IETF) and the World Wide Web Consortium (W3C ), culminating in the publication of the so-called RFC (Requests for Comments), are documents that describe various aspects of the operation of the Internet and other computer networks, such as protocols, procedures, etc.
The first definition was HTTP/1.1, published in RFC 2068 in 1997, and then replaced by RFC 2616 in 1999.
Its successor, HTTP/2, was published in May 2015, is currently supported by most web browsers and web servers.
In recent times, Google and other companies promote (and practically force) websites to switch to HTTPS technology.
General HTTP operation
In the client-server model, HTTP functions as a request-response protocol.The typical case is the web browser (it is the client on a computer) and the website that is hosted on a server.
The client sends an HTTP request (or request or request) message to the server.The server, which provides resources such as HTML files and other web content, returns a response message to the client.
This response contains information about the status of the request and may also have content in the message body.
HTTP messages are plain text which makes it more readable and easy to debug.This has the disadvantage of making longer messages.
The web browser is an example of a user agent (user agent or UA).Other types of user agent can be the web crawlers that use Internet search engines for indexing content, mobile apps and any other software that access or display web content.
HTTP is designed to allow intermediate network elements to improve or allow communications between clients and servers.For example, high traffic websites often benefit from cache servers that deliver content instead of the server to speed up response time.
Web browsers also cache web resources previously accessed for reuse them and thus load them faster, reducing network traffic.
HTTP is an application layer protocol designed within the framework of the Internet Protocol Suite (TCP/IP), where its definition implies a transport layer protocol (usually TCP).Although HTTP can be adapted for other protocols such as SSDP or UDP (in HTTPU for example).
HTTP resources are identified and located in a network using addresses URLs, using the http and https URI schemes
The URIs and hyperlinks in an HTML document form the interlinked hypertext documents.
HTTP/1.1 is a revision of the original version of HTTP (HTTP/1.0).In HTTP/1.0 a separate connection is made to the same server each time a resource is requested.In both HTTP/1.1 a connection can be reused multiple times to download images, scripts, CSS files, etc.after the html page has been delivered.Therefore, HTTP/1.1 communications experience less latency.
HTTP versions
-1991: HTTP version 0.9, only supports the GET command.Within the request itself The HTTP version is not specified, nor header.It also does not support the POST method.
-May 1996: HTTP/1.0, the HTTP version is specified in the request, allows GET, HEAD and POST methods.It is still used, usually on proxy servers.
-June 1999: HTTP/1.1, persistent connections were activated by default, working correctly with proxies.It allows the client to send multiple requests at once using the same connection (pipelining), allowing to reduce the latency (Round-Trip delay) of each request.It is the version most used today.
-2000: HTTP/1.2: the first drafts of this version were from 1995 where the Protocol Extension Protocol, abbreviated PEP, is proposed for HTTP.The W3C made them and was sent to the IETF.February 2000.
-May 2015: HTTP/2.Start writing in 2012.The basics continue unchanged from the previous version.The improvements are concentrated in the packaging of data and in the transport.For example, add the use of a single connection, compression of headers and also the server push service (form of communication in which the sending request originates from the server, as opposed to the pull technology, in which the request originates from the client).
RFC 2145 describes the use of HTTP version numbers.The client tells the server at the beginning of the request the version it uses, and the server uses the same or a previous one in your response.
HTTP response numerical codes
The web server responds to each request with a response code that can be:
-1xx: Informative answers, indicating that the request was received and is being processed.The most common is 100.
-2xx: Correct answers, where it indicates that the request was processed correctly.The typical is 200 (OK).
-3xx: Redirect responses, indicates that the client must perform more actions to finalize this request.
-4xx: Errors caused by the client, where it indicates that an error has occurred while the request was being processed probably because the client did something wrong, usually because the URL is incorrect, which is the most typical error, 404.Also the 403-Forbidden (prohibited) is usual.
-5xx: Errors caused by the server, this indicates that an error has occurred while processing the request due to a server failure.en 500-Internal Server Error.
Example of an HTTP dialog
HTTPS
HTTPS is a variant encrypted using SSL.
To more information see: HTTPS.
Google's change to HTTPS
Read: Why does Chrome now mention unsafe websites?
Network technologies and protocols *
Application level
DNS, FTP, HTTP, IMAP, IRC, NFS, NNTP, NTP, POP3, SMB/CIFS, SMTP, SNMP, SSH, Telnet, SIP...
Presentation level
ASN.1, MIME, SSL/TLS, XML...
Session level
NetBIOS...
Transport level
SCTP, SPX, TCP, UDP...
Network level
AppleTalk, IP, IPX, NetBEUI, X.25...
Link level
ATM, Ethernet, Frame Relay, HDLC, PPP, Token Ring, Wi-Fi, STP...
Physical level
Coaxial cable, fiber optic, twisted pair, microwave, radio, RS-232...
* Following the OSI model
Questions? needs more information?
Write and we will respond to your email
Http Definition (Hypertext Transfer Protocol) >>>>> Download Now
ReplyDelete>>>>> Download Full
Http Definition (Hypertext Transfer Protocol) >>>>> Download LINK
>>>>> Download Now
Http Definition (Hypertext Transfer Protocol) >>>>> Download Full
>>>>> Download LINK zC