Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Forwarded HTTP Extension (RFC7239)

IP.com Disclosure Number: IPCOM000237199D
Original Publication Date: 2014-Jun-01
Included in the Prior Art Database: 2014-Jun-08
Document File: 32 page(s) / 35K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Petersson: AUTHOR [+2]

Abstract

In today's HTTP landscape, there are a multitude of different applications that act as proxies for the user agents. In many cases, these proxies exists without the action or knowledge of the end-user. These cases occur, for example, when the proxy exists as a part of the infrastructure within the organization running the web server. Such proxies may be used for features such as load balancing or crypto offload. Another example is when the proxy is used within the same organization as the user, and the proxy is used to cache resources. However, these proxies make the requests appear as if they originated from the proxy's IP address, and they may change other information in the original request. This represents a loss of information from the original request.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Internet Engineering Task Force (IETF)                      A. Petersson Request for Comments: 7239                                    M. Nilsson Category: Standards Track                                 Opera Software ISSN: 2070-1721                                                June 2014

                         Forwarded HTTP Extension

Abstract

   This document defines an HTTP extension header field that allows    proxy components to disclose information lost in the proxying    process, for example, the originating IP address of a request or IP    address of the proxy on the user-agent-facing interface.  In a path    of proxying components, this makes it possible to arrange it so that    each subsequent component will have access to, for example, all IP    addresses used in the chain of proxied HTTP requests.

   This document also specifies guidelines for a proxy administrator to    anonymize the origin of a request.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7239.

Petersson & Nilsson          Standards Track                    [Page 1]
 RFC 7239                Forwarded HTTP Extension               June 2014

 Copyright Notice

   Copyright (c) 2014 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    (http://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

   2. Notational Conventions ..........................................4

   3. Syntax Notations ................................................4

   4. Forwarded HTTP Header Field .....................................4

   5. Parameters ...