The Proxy-Status HTTP Response Header Field
draft-ietf-httpbis-proxy-status-02
HTTP M. Nottingham
Internet-Draft Fastly
Intended status: Standards Track P. Sikora
Expires: February 12, 2021 Google
August 11, 2020
The Proxy-Status HTTP Response Header Field
draft-ietf-httpbis-proxy-status-02
Abstract
This document defines the Proxy-Status HTTP field to convey the
details of intermediary handling of responses, including generated
errors.
Note to Readers
_RFC EDITOR: please remove this section before publication_
Discussion of this draft takes place on the HTTP working group
mailing list (ietf-http-wg@w3.org), which is archived at
https://lists.w3.org/Archives/Public/ietf-http-wg/ [1].
Working Group information can be found at https://httpwg.org/ [2];
source code and issues list for this draft can be found at
https://github.com/httpwg/http-extensions/labels/proxy-status [3].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 12, 2021.
Nottingham & Sikora Expires February 12, 2021 [Page 1]
Internet-Draft Proxy-Status August 2020
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 4
2. The Proxy-Status HTTP Field . . . . . . . . . . . . . . . . . 4
2.1. Proxy-Status Parameters . . . . . . . . . . . . . . . . . 5
2.1.1. next-hop . . . . . . . . . . . . . . . . . . . . . . 5
2.1.2. next-protocol . . . . . . . . . . . . . . . . . . . . 5
2.1.3. error . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.4. details . . . . . . . . . . . . . . . . . . . . . . . 7
2.2. Defining New Proxy-Status Parameters . . . . . . . . . . 7
2.3. Proxy Error Types . . . . . . . . . . . . . . . . . . . . 8
2.3.1. DNS Timeout . . . . . . . . . . . . . . . . . . . . . 8
2.3.2. DNS Error . . . . . . . . . . . . . . . . . . . . . . 8
2.3.3. Destination Not Found . . . . . . . . . . . . . . . . 8
2.3.4. Destination Unavailable . . . . . . . . . . . . . . . 9
2.3.5. Destination IP Prohibited . . . . . . . . . . . . . . 9
2.3.6. Destination IP Unroutable . . . . . . . . . . . . . . 9
2.3.7. Connection Refused . . . . . . . . . . . . . . . . . 9
2.3.8. Connection Terminated . . . . . . . . . . . . . . . . 10
2.3.9. Connection Timeout . . . . . . . . . . . . . . . . . 10
2.3.10. Connection Read Timeout . . . . . . . . . . . . . . . 10
2.3.11. Connection Write Timeout . . . . . . . . . . . . . . 10
2.3.12. Connection Limit Reached . . . . . . . . . . . . . . 11
2.3.13. TLS Protocol Error . . . . . . . . . . . . . . . . . 11
2.3.14. TLS Certificate Error . . . . . . . . . . . . . . . . 11
2.3.15. TLS Alert Received . . . . . . . . . . . . . . . . . 11
2.3.16. HTTP Request Error . . . . . . . . . . . . . . . . . 12
2.3.17. HTTP Request Denied . . . . . . . . . . . . . . . . . 12
2.3.18. HTTP Incomplete Response . . . . . . . . . . . . . . 12
2.3.19. HTTP Response Header Block Too Large . . . . . . . . 13
2.3.20. HTTP Response Header Too Large . . . . . . . . . . . 13
2.3.21. HTTP Response Body Too Large . . . . . . . . . . . . 13
Nottingham & Sikora Expires February 12, 2021 [Page 2]
Show full document text