IETF - Internet Engineering Task Force, founded in 1986, is the premier standards development organization (SDO) for internet.
The RFC (Request for comments) produced by the IETFS cover many aspects of computer networking.
The RFC series has two sub-series, STDs and BCPs, with each numbered STD and BCP comprising one or more RFCs.
STDs are Internet Standard RFCs and BCPs are RFCs that describe **Best Current Practices in the Internet, some of which are administrative processes for the IETF.
Only some RFCs are standards.
The canonical place to find RFCs is the RFC Editor Web Site Some key information is missing there, so most people use tools.ietf.org Plain text RFCs are difficult to read bordering and ugly. For more usable RFCs, you can use third-party repositories greenbytes keeps a list of WebDAV-related RFCs, and theHTTP Working Group maintains a selection of those related to HTTP.
The ASCII text RFCs (e.g., at the RFC Editor site) don't tell you what documents update or obsolete the document you are currently looking at.
It is necessary to read not only the directly relevant text but also (at a minimum) anything that it references, whether that is in the same spec or a different one. In a pinch, reading any potentially related sections will help immensely, if you can not read the whole document.
Many protocols set up IANA registries to manage their extension points; These, not the specifications, are the sources of truth. For example, the canonical list of HTTP methods is in this registry, not any of the HTTP specifications.
Another very common pitfall is to skim the specification for examples and implement what they do. Examples typically get the least amount of attention from authors. They are very often the least reliable parts of the spec.
From Requests is not a built-in library. Use url lib.request to stick to standard-library. [RFC 7230, part 1 Message Syntax and Routing] (https://datatracker.ietf.org/doc/html/rfc7230)
Tras entender los RFC.... La ultima version June 2022 de la especificaciónn es la 9112 conocida también como std99
The target of an HTTP request is called Resource. Each resource is identified by a URI: Uniform Resource Identifier
A) URL is the most common URI. HTTP messages are how data is exchanged between a server and a client. Requests Responses HTTP/1.1 open text HTTP/2 Binary Framing
Requests and responses have similar structures:
- Start-line: SINGLE LINE. Request description or response status.
- Set of headers
- Empty blank lines
- Body}