Deterministic URI Encoding
draft-montenegro-httpbis-uri-encoding-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Osama Mazahir, Dave Thaler , Matthew Cox, Gabriel Montenegro | ||
| Last updated | 2014-08-17 (Latest revision 2014-02-13) | ||
| 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
The "http" and "https" URI schemes do not have a fixed character encoding. This document defines HTTP headers to enable an explicit indication of the character encoding.
Authors
Osama Mazahir
Dave Thaler
Matthew Cox
Gabriel Montenegro
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)