From 44c1cb0d7f6f088ea76644f85b7bc59856cd929b Mon Sep 17 00:00:00 2001 From: Hamish Willee Date: Tue, 27 Feb 2024 09:18:24 +1100 Subject: [PATCH] HTTP messages are not ASCII encoded (#32434) * HTTP messages are not ASCII encoded * Remove altogether --------- Co-authored-by: Brian Thomas Smith --- files/en-us/web/http/messages/index.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/files/en-us/web/http/messages/index.md b/files/en-us/web/http/messages/index.md index aadc2f05c3149b5..436cd45b894daf7 100644 --- a/files/en-us/web/http/messages/index.md +++ b/files/en-us/web/http/messages/index.md @@ -8,8 +8,6 @@ page-type: guide HTTP messages are how data is exchanged between a server and a client. There are two types of messages: _requests_ sent by the client to trigger an action on the server, and _responses_, the answer from the server. -HTTP messages are composed of textual information encoded in ASCII, and span over multiple lines. In HTTP/1.1, and earlier versions of the protocol, these messages were openly sent across the connection. In HTTP/2, the once human-readable message is now divided up into HTTP frames, providing optimization and performance improvements. - Web developers, or webmasters, rarely craft these textual HTTP messages themselves: software, a Web browser, proxy, or Web server, perform this action. They provide HTTP messages through config files (for proxies or servers), APIs (for browsers), or other interfaces. ![From a user-, script-, or server- generated event, an HTTP/1.x msg is generated, and if HTTP/2 is in use, it is binary framed into an HTTP/2 stream, then sent.](httpmsg2.png)