X-RequestOrigin
draft-megacz-x-requestorigin-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Adam Megacz , Deneb Meketa | ||
| Last updated | 2003-09-15 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Security policies are often implemented by network intermediaries such as routers and proxies. These intermediaries are unable to distinguish between requests from requests initiated by a user and requests initiated by untrusted mobile code running on the user's machine. This document describes the X-RequestOrigin hop-by-hop HTTP header, which an HTTP client uses to allow intermediate proxies to make this distinction.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)