Loop Detection in Content Delivery Networks (CDNs)
RFC 8586
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2022-11-10
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2019-08-19
|
Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events' |
|
2019-08-19
|
Gunter Van de Velde | Assignment of request for Last Call review by OPSDIR to Tim Wicinski was marked no-response |
|
2019-04-25
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2019-04-24
|
(System) | Received changes through RFC Editor sync (created alias RFC 8586, changed title to 'Loop Detection in Content Delivery Networks (CDNs)', changed abstract to 'This … Received changes through RFC Editor sync (created alias RFC 8586, changed title to 'Loop Detection in Content Delivery Networks (CDNs)', changed abstract to '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.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-04-24, changed IESG state to RFC Published) |
|
2019-04-24
|
(System) | RFC published |