RFC 8441 Quiz

Q1: In HTTP/2, WebSockets are bootstrapped primarily using

Multiple Choice

A. The HTTP/1.1 Upgrade header B. Extended CONNECT C. A DNS SRV record

**Explanation:** **Correct (B):** HTTP/2 does not use the same connection upgrade model as HTTP/1.1, so extended CONNECT is used

Q2: What does using WebSockets over HTTP/2 avoid compared to the HTTP/1.1 upgrade approach

Multiple Choice

A. Any need for encryption B. Any HTTP semantics C. Tying a WebSocket to a dedicated TCP connection

**Explanation:** **Correct (C):** HTTP/2 multiplexes streams over one connection, so a WebSocket can live in a stream

Q3: A client uses an HTTP/2 CONNECT for a WebSocket. What should it signal as the target protocol

Multiple Choice

A. websocket B. http C. tls

**Explanation:** **Correct (A):** The target protocol is indicated as websocket in the extended CONNECT mechanism

Q4: Which are still relevant for WebSocket semantics when using HTTP/2 bootstrapping (select all)

Multi-Select

A. WebSocket message framing and opcode rules B. The need for origin based authorization checks in browsers C. Application authentication and authorization design D. The HTTP/1.1 Connection header requirement

**Explanation:** **Correct (A,B,C):** The bootstrapping changes, but the security and application concerns remain **Options:** - D (incorrect): HTTP/2 does not use the same Connection header model

Q5: A proxy only supports HTTP/2 and blocks Upgrade. What is a practical consequence for WebSockets

Multiple Choice

A. WebSockets become impossible B. You may need the HTTP/2 bootstrapping approach instead of HTTP/1.1 upgrade C. You must always downgrade to long polling

**Explanation:** **Correct (B):** HTTP/2 environments can use extended CONNECT to establish the WebSocket semantics

Q6: Which HTTP method is central to the HTTP/2 WebSocket bootstrapping approach (one word)

Short Text

**Explanation:** **Correct:** CONNECT

Bootstrapping WebSockets with HTTP/2

References (URLs)

Q1: In HTTP/2, WebSockets are bootstrapped primarily using

Q2: What does using WebSockets over HTTP/2 avoid compared to the HTTP/1.1 upgrade approach

Q3: A client uses an HTTP/2 CONNECT for a WebSocket. What should it signal as the target protocol

Q4: Which are still relevant for WebSocket semantics when using HTTP/2 bootstrapping (select all)

Q5: A proxy only supports HTTP/2 and blocks Upgrade. What is a practical consequence for WebSockets

Q6: Which HTTP method is central to the HTTP/2 WebSocket bootstrapping approach (one word)