Wildcards in the Accept-Charset Header
draft-holtman-http-wildcards-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Koen Holtman | ||
Last updated | 1997-03-20 | ||
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/1.1 specification (RFC 2068) defines an Accept-Charset header, but fails to define a wildcard '*' which could be used in this header to match all character sets. This proposal corrects this omission.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)