Reject ambiguous HTTP/1.1 message framing at every intermediary

Use this document to resolve one bounded operational decision: Reject ambiguous HTTP/1.1 message framing at every intermediary. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 9112 — HTTP/1.1 from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• An HTTP/1.1 recipient parses the message as octets, not an unconstrained Unicode stream, before interpreting extracted protocol elements. The research record locates this support at Section 2.2 (Message Parsing).
• A sender must not combine Content-Length with Transfer-Encoding; if both arrive, Transfer-Encoding wins and a forwarding intermediary first removes Content-Length. The research record locates this support at Sections 6.1 (Transfer-Encoding), 6.2 (Content-Length), and 6.3 (Message Body Length), rule 3.
• Invalid or conflicting Content-Length framing is unrecoverable unless every valid list value is identical, with requests rejected and response recipients closing the upstream connection. The research record locates this support at Section 6.3 (Message Body Length), rule 5.

Keep the evidence boundary at these traced claims. They support a review of clients, origin services, intermediaries, caches, proxies, gateways, protocol versions, and security-policy enforcement points; they do not support conclusions outside the source’s stated conditions.

What the source does not establish

This RFC evidence supports only the named web or transport decision; it does not prove browser, intermediary, library, or service compatibility. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that DNS, certificates, identity providers, time, content delivery, network paths, and application ownership are healthy. Documented options are review inputs, not universal mandates.

Applicability questions

• For source statement 1 at Section 2.2 (Message Parsing), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Sections 6.1 (Transfer-Encoding), 6.2 (Content-Length), and 6.3 (Message Body Length), rule 3, which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 6.3 (Message Body Length), rule 5, which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of clients, origin services, intermediaries, caches, proxies, gateways, protocol versions, and security-policy enforcement points are in and out of scope?
• Which condition in DNS, certificates, identity providers, time, content delivery, network paths, and application ownership must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of clients, origin services, intermediaries, caches, proxies, gateways, protocol versions, and security-policy enforcement points, observed and expected states, owner, and reason for deviation.

For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check DNS, certificates, identity providers, time, content delivery, network paths, and application ownership in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.

Verification and evidence

A reviewer should be able to retrace the decision from Section 2.2 (Message Parsing); Sections 6.1 (Transfer-Encoding), 6.2 (Content-Length), and 6.3 (Message Body Length), rule 3; Section 6.3 (Message Body Length), rule 5 through request and response captures, negotiated protocol details, headers, cache behavior, certificate state, and server or proxy logs. Record what was collected, where, when, by whom, and which system or role it represents.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• RFC 9112 — HTTP/1.1 — RFC Editor / Internet Engineering Task Force