Edit ISSUE-250: Non-ASCII not permitted in extensions

Nickname:

Title:

State:

Product:

Raised By:

Description:

Add notes (no markup allowed, URIs get automatically hyperlinked):

Related emails:

  1. Resolving Last Call issues to TPE (from jbrookman@cdt.org on 2014-09-08) (from jbrookman@cdt.org on 2014-09-08)
  2. Re: tracking-ISSUE-250: Non-ASCII not permitted in extensions [TPE Last Call] (from fielding@gbiv.com on 2014-08-26) (from fielding@gbiv.com on 2014-08-26)
  3. tracking-ISSUE-250: Non-ASCII not permitted in extensions [TPE Last Call] (from sysbot+tracker@w3.org on 2014-07-13) (from sysbot+tracker@w3.org on 2014-07-13)

Related notes:

WONTFIX. Non-ASCII characters are not interoperable when parsed within an HTTP header field unless they are first encoded as ASCII. Since there is no current need for extensions and the field is not intended for humans, there is no justification for the complexity of arbitrary unicode.

Roy Fielding, 27 Aug 2014, 01:07:35


Matthias Schunter <matthias.schunter@intel.com>, Chair, Bert Bos <bert@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $