RFC 8586: Loop Detection in Content Delivery Networks (CDNs)
In plain English — editorial summary, not part of the RFC
This document defines the CDN-Loop request header field for HTTP. CDN-Loop addresses an operational need that occurs when an HTTP request is intentionally forwarded between Content Delivery Networks (CDNs), but is then accidentally or maliciously re-routed back into the original CDN causing a non-terminating loop. The new header field can be used to identify the error and terminate the loop.
Document record
- Document ID
- RFC8586
- Published
- April 2019
- Authors
- S. Ludin; M. Nottingham; N. Sullivan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8587NFS Version 4.0 Trunking UpdateCurrent
May 2019
- RFC 8613Object Security for Constrained RESTful Environments (OSCORE)Current
July 2019
- RFC 8622A Lower-Effort Per-Hop Behavior (LE PHB) for Differentiated ServicesCurrent
June 2019
- RFC 8540Stream Control Transmission Protocol: Errata and Issues in RFC 4960Obsoleted
February 2019
- RFC 8516"Too Many Requests" Response Code for the Constrained Application ProtocolCurrent
January 2019
- RFC 8511TCP Alternative Backoff with ECN (ABE)Current
December 2018
- RFC 8673HTTP Random Access and Live ContentCurrent
November 2019
- RFC 8680Forward Error Correction (FEC) Framework Extension to Sliding Window CodesCurrent
January 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?