The "hxxp" and "hxxps" URI Schemes
draft-salgado-hxxp-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2017-11-13 (latest revision 2017-05-09) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-salgado-hxxp-01.txt
https://www.ietf.org/archive/id/draft-salgado-hxxp-01.txt
Abstract
This document describes the "hxxp" and "hxxps" URI schemes, which are widely used by the security community to obfuscate an http or https URI to avoid being accidentaly interpreted and loaded by a web browser or user-agent.
Authors
Hugo Salgado (hsalgado@nic.cl)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)