HTTP

Question 1

HTTP

Answer 1

-Hyper Text Transfer Protocol
-Transmission of Hyper Text across the World Wide Web
-Request:Response Model between Client:Server
-Stateless: info is not retained about the client on the server and previous interaction data

Question 2

HTTP Methods

Answer 2

-GET, POST, PUT , PATCH, DELETE, OPTIONS, HEAD

Question 3

GET

Answer 3

Retrieve data

Question 4

POST

Answer 4

Send data

Question 5

PUT

Answer 5

Update or replace resource on a server

Question 6

PATCH

Answer 6

Partially update a resource on a server

Question 7

DELETE

Answer 7

Remove resource on a server

Question 8

OPTIONS

Answer 8

Discover HTTP methods supported by the server

Question 9

HEAD

Answer 9

Retrieve headers for a resource without a body

Question 10

1xx Status Code

Answer 10

Processing

Question 11

2xx

Answer 11

Success

Question 12

3xx

Answer 12

Redirection

Question 13

4xx

Answer 13

Client Error

Question 14

5xx

Answer 14

Server Error

Question 15

Headers

Answer 15

Convey meta data about the request. Examples: Content-Type, Authorization, Accept, Cookie (contains stateful state from client), Cache-Control

Question 16

HTTP/1

Answer 16

-1997
-text-based communication
-Persistent connections, no need to re-establish connection on every request. Client can send Connection: close in the header to terminate connection
-Pipelining: sending multiple requests without waiting for responses. Caveat is “head-of-line’ blocking where the slower response blocks other responses
-Chunked Transfer Encoding: sending data in chunks without the server needing to know the final, total data size (e.g., streaming)
-Caching support: Cache-Control and and Expires
-High latency

Question 17

HTTP/2

Answer 17

-2015
-binary framing communication, more efficient and easier to parse
-multiplexing: multiple concurrent requests over the same connection.
-header compression: HPACK compression to compress redundant headers
-stream prioritization: certain data takes higher-priority eg html over css
-server push: servers proactively push data to the client
-Limitations: relies on TCP so HOL blocking can occur if fragmentation occurs at the transport layer, still SINGLE streams

Question 18

HTTP/3

Answer 18

-2020
-Essentially rebuilding HTTP /2 to run on QUIC to replace TCP; and QUIC was built on UDP (a bare-bones equivalent of TCP only concerned with port numbers) that is easily deployable and scalable
-QUIC reduces HOL blocking by receiving data via multiple independent streams where order does not matter vs TCP with one continueous, ordered stream