W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2012

feedback on draft-reschke-basicauth-enc-04, "3. The 'encoding' auth-param"

From: Alexei Khlebnikov <alexei.khlebnikov@opera.com>
Date: Mon, 30 Jan 2012 13:20:43 +0100
To: ietf-http-wg@w3.org
Message-ID: <op.v8wcktoyockn2m@alexeik-desktop.oslo.osa>
Hi,

My feedback on  
<http://greenbytes.de/tech/webdav/draft-reschke-basicauth-enc-04.html#encoding>:

Was it considered to name the new parameter "charset" instead of  
"encoding"?

I can see the following advantages of "charset":

1) "Charset" is unambigous. "Encoding" is ambigous, it can refer to many  
things: base64, quoted-printable, chunked-coding, gzip-compression, etc.

2) "Charset" is already used in the HTTP protocol, so it is good to use  
the same word for consistency:

Content-Type: text/html; charset=UTF-8


-- 
Alexei.
Received on Monday, 30 January 2012 12:21:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:54 GMT