[RESEARCH] HTTP Protocol study list

[LeaYeh]

• 7230: https://www.rfc-editor.org/rfc/pdfrfc/rfc7230.txt.pdf
  • [ ] @LeaYeh 6, 9
  • [ ] @yenthing 1, 2, 3
  • [ ] @leske42 4
• 7231: https://www.rfc-editor.org/rfc/pdfrfc/rfc7231.txt.pdf
  • [ ] @leske42 5.3, 6, 7
  • [ ] @yenthing 3, 4, 5, 6
  • [ ] @LeaYeh 6, 9
• 7232: https://www.rfc-editor.org/rfc/pdfrfc/rfc7232.txt.pdf
  • [ ] @leske42 4
  • [ ] @yenthing 4
  • [ ] @LeaYeh 4
• 7233: https://www.rfc-editor.org/rfc/pdfrfc/rfc7233.txt.pdf
• 7234: https://www.rfc-editor.org/rfc/pdfrfc/rfc7234.txt.pdf
  • BONUS
• 7235: https://www.rfc-editor.org/rfc/pdfrfc/rfc7235.txt.pdf
  • Authentication

[LeaYeh]

The HTTP/1.1 standard is defined by a series of core documents, typically published as RFCs (Request for Comments). Here is a list of the core documents that define the HTTP/1.1 standard:

• RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"
  • Defines the message syntax, message format, connection management, and request/response mechanisms of HTTP/1.1.
• RFC 7231: "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content"
  • Describes the semantics of HTTP/1.1, including methods (such as GET, POST), status codes (like 200, 404), header fields (such as Content-Type), and more.
• RFC 7232: "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests"
  • Provides details on the conditional request mechanisms in HTTP, covering headers like If-Modified-Since and If-None-Match, which are used for cache management and resource update checks.
• RFC 7233: "Hypertext Transfer Protocol (HTTP/1.1): Range Requests"
  • Defines the HTTP range request feature, allowing clients to request specific parts of a resource, such as for resuming interrupted downloads.
• RFC 7234: "Hypertext Transfer Protocol (HTTP/1.1): Caching"
  • Discusses HTTP caching mechanisms, describing how HTTP responses can be cached on clients and proxy servers to improve performance and reduce bandwidth usage.
• RFC 7235: "Hypertext Transfer Protocol (HTTP/1.1): Authentication"
  • Specifies the HTTP authentication framework, including mechanisms like Basic Authentication and Digest Authentication.

[LeaYeh]

@yenthing https://datatracker.ietf.org/doc/html/rfc3986#section-3

the state machine of URI analyzation needs to follow the protocol.

• scheme = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )
• authority = [ userinfo "@" ] host [ ":" port ]
• host = IP-literal / IPv4address / reg-name
• port = *DIGIT

• path = path-abempty ; begins with "/" or is empty / path-absolute ; begins with "/" but not "//" / path-noscheme ; begins with a non-colon segment / path-rootless ; begins with a segment / path-empty ; zero characters

  path-abempty = ( "/" segment ) path-absolute = "/" [ segment-nz ( "/" segment ) ] path-noscheme = segment-nz-nc ( "/" segment ) path-rootless = segment-nz ( "/" segment ) path-empty = 0 segment = pchar segment-nz = 1pchar segment-nz-nc = 1*( unreserved / pct-encoded / sub-delims / "@" ) ; non-zero-length segment without any colon ":" pchar = unreserved / pct-encoded / sub-delims / ":" / "@"

• query = *( pchar / "/" / "?" )

[LeaYeh]

I feel like I need to read all of the documents because they are highly related....

[yenthing]

[7230] https://www.rfc-editor.org/rfc/pdfrfc/rfc7230.txt.pdf - Message Syntax and Routing

Chapter 1:

This HTTP/1.1 specification obsoletes RFC 2616 and RFC 2145.

Chapter 2: HTTP enables the use of intermediaries to satisfy requests through a

chain of connections. There are three common forms of HTTP intermediary: proxy, gateway, and tunnel. In some cases, a single intermediary might act as an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request.

A request or response message that travels the whole chain will pass through four separate connections. Although the diagram is linear, each participant might be engaged in multiple, simultaneous communications. For example, B might be receiving requests from many clients other than A, and/or forwarding requests to servers other than C, at the same time that it is handling A’s request. Likewise, later requests might be sent through a different path of connections, often based on dynamic configuration for load balancing.

• proxy: is a message-forwarding agent that is selected by the client, usually via local configuration rules, to receive requests for some type(s) of absolute URI and attempt to satisfy those requests via translation through the HTTP interface.
• gateway (a.k.a. "reverse proxy") is an intermediary that acts as an origin server for the outbound connection but translates received requests and forwards them inbound to another server or servers.

  A server MUST NOT assume that two requests on the same connection are from the same user agent unless the connection is secured and specific to that agent.

• cache is a local store of previous response messages and the subsystem that controls its message storage, retrieval, and deletion.

  Still reading from 2.4

[leske42]

Guys all of this is obsolete lol