Hypertext Transfer Protocol (HTTP/1.1)¶
Fielding, R., & Reschke, J. (2014). Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content.
Cited by¶
1 citation across 1 artifact.
Primes¶
- Idempotence
- clients use this contract to decide whether automatic retry is safe.
SupportedVerified against the work's full text
RFC 7231 section 4.2.2 explains idempotence matters because a client can automatically resend such a request after a connection failure, knowing the effect is the same.
“Idempotent methods are distinguished because the request can be repeated automatically if a communication failure occurs before the client is able to read the server's response.”
- clients use this contract to decide whether automatic retry is safe.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported. Each verdict is shown under its citation below, with what in the work backs the sentence.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:18ba418fe822 · see in the full table