The "hxxp" and "hxxps" URI Schemes
draft-salgado-hxxp-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-05-09
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force H. Salgado
Internet-Draft NIC Chile
Intended status: Informational May 8, 2017
Expires: November 9, 2017
The "hxxp" and "hxxps" URI Schemes
draft-salgado-hxxp-01
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.
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 http://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 November 9, 2017.
Copyright Notice
Copyright (c) 2017 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.
Salgado Expires November 9, 2017 [Page 1]
Internet-Draft The "hxxp" and "hxxps" URI Schemes May 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. URI Scheme Specification . . . . . . . . . . . . . . . . . . 3
2.1. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . 3
2.2. URI Scheme Semantics . . . . . . . . . . . . . . . . . . 3
2.3. Encoding Considerations . . . . . . . . . . . . . . . . . 3
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4.1. URI Scheme Registration . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
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.
These schemes are used in case the resource is dangerous and there is
security risks on being automatically processed by an application,
such a pre-loading mechanism in web user agents. It also prevents
the creation of "clickables" areas in user interfaces, which could
detect http or https URIs automatically.
The purpose of this registration is to document its use, prevent any
registration of this scheme in the future, explicitly recommend to
web application developers to never act with this URI schemes in any
way, and provide a safe method for the security community to share
malicious information. These schemes must not be treated as an http
or https schemes, and must not be identified as web resources. Its
consumption is only for humans and documentation, and should be
handled with caution by security professionals.
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Salgado Expires November 9, 2017 [Page 2]
Show full document text