HTTP Versions Flashcards

1
Q

Called the one-line protocol because requests consisted on only one line.

A

HTTP/0.9

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

The only method in HTTP/0.9

A

GET

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

These are the only files that existed on the web to be sent over HTTP as there was no content type to indicate MIME Type

A

HTML Files

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

HTPP response messages on HTTP/0.9 contained only the ___________

A

document requested.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Response messages didn’t have status codes or reason phrases.

A

HTTP/0.9

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

In case of an error in HTTP/0.9, a ___________ would be sent with a description of the error.

A

a specific HTML file

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Features were introduced over 1991-1995 experimentally. Interoperability problems were common.

A

HTTP/1.0

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Response messages were now prefixed with a STATUS LINE and HEADERS were added to request and response messages.

A

HTTP/1.0

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

With the addition of headers, the following became possible: (3)

A

Content negotiation
Authorization
Caching

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

In HTTP/1.0, request and response message were _____________ but the response payload could be any other content type.

A

ASCII-encoded

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

The first specification of HTTP/1.1 was published in early ____.

A

1997

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Now known as the standardized protocol.

A

HTTP/1.1

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

3 new features introduced in HTTP/1.1.

A

Connection reuse
Pipelining
Chunked responses

also added content negotiations options (language, encoding, type)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Meant that the TCP connection could be kept alive for further requests, saving time it took to load all resources in the web page.

A

Connection reuse

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Allowed the client to send a second request before a response was received for the first request.

A

Pipelining

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Large responses could be split up over several messages.

A

Chunked responses

17
Q

HTTP/2.0 was offiicialy standardized on _______.

18
Q

HTTP/2.0 is currently used by _______ of websites.

19
Q

The primary focus of HTTP/2.0.

A

Improving transport performance

20
Q

Improving transport performance was achieved by focusing on:

A

reducing latency
increasing throughput

21
Q

In HTTP/2.0, requests and response can’t be manually created/read anymore.

A

Binary Protocol

22
Q

Advantages of binary protocols:

A

More efficient to parse
Messages take up less space
Less error-prone

23
Q

In HTTP/2.0, multiple requests and responses can be in flight at the same time.

A

Multiplexing

24
Q

In HTTP/2.0, headers are __________ to remove duplication and save overhead on data transfer.

A

Compressed

25
Q

Allow servers to populate data in a client cache, in advance of the data being required.

A

Server Push

26
Q

HTTP/3.0 is currently in the works and a draft has been released in __________.

A

January 2021