[http-auth] Fwd: [Bug 41489] HTTP authentication does not support non-ISO-8859-1 characters

Julian Reschke <julian.reschke@gmx.de> Mon, 08 April 2013 14:22 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFB6721F93C6 for <http-auth@ietfa.amsl.com>; Mon, 8 Apr 2013 07:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YVCfCboOBZVx for <http-auth@ietfa.amsl.com>; Mon, 8 Apr 2013 07:22:41 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id D394021F976B for <http-auth@ietf.org>; Mon, 8 Apr 2013 07:22:40 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.1]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0M1TnD-1Uj5KY09m5-00tSR3 for <http-auth@ietf.org>; Mon, 08 Apr 2013 16:22:39 +0200
Received: (qmail invoked by alias); 08 Apr 2013 14:22:38 -0000
Received: from p54BB25AB.dip.t-dialin.net (EHLO [192.168.178.36]) [84.187.37.171] by mail.gmx.net (mp001) with SMTP; 08 Apr 2013 16:22:38 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+Q94g95eSQo+su/WEAT1QPUtmxbMCef6T7eoX4gK PS/O7HgeeDdY5x
Message-ID: <5162D2AD.5070408@gmx.de>
Date: Mon, 08 Apr 2013 16:22:37 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "http-auth@ietf.org" <http-auth@ietf.org>
References: <bug-41489-52340-spkEu59l23@https.bugzilla.mozilla.org/>
In-Reply-To: <bug-41489-52340-spkEu59l23@https.bugzilla.mozilla.org/>
X-Forwarded-Message-Id: <bug-41489-52340-spkEu59l23@https.bugzilla.mozilla.org/>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Subject: [http-auth] Fwd: [Bug 41489] HTTP authentication does not support non-ISO-8859-1 characters
X-BeenThere: http-auth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: HTTP authentication methods <http-auth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-auth>, <mailto:http-auth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-auth>
List-Post: <mailto:http-auth@ietf.org>
List-Help: <mailto:http-auth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-auth>, <mailto:http-auth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2013 14:22:42 -0000

FYI and so it's archived:

<http://tools.ietf.org/html/rfc2831#page-5> defines a "charset" 
parameter for Digest/SASL. This is *very* similar to what my draft 
proposes for Basic and Digest in HTTP; maybe it should simply align with 
that.

Best regards, Julian

-------- Original Message --------
Subject: [Bug 41489] HTTP authentication does not support non-ISO-8859-1 
characters
Date: Mon, 08 Apr 2013 13:38:11 +0000
From: bugzilla-daemon@mozilla.org
To: julian.reschke@gmx.de

https://bugzilla.mozilla.org/show_bug.cgi?id=41489

ggo <ggo98@yahoo.com> changed:

            What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #734492| 
|review?(bsmith@mozilla.com)
               Flags|                            |

--- Comment #122 from ggo <ggo98@yahoo.com> 2013-04-08 06:38:11 PDT ---
Comment on attachment 734492
   --> https://bugzilla.mozilla.org/attachment.cgi?id=734492
Allow utf-8 encoded username in digest authentication response header.

This patch allows the http digest authentication module to send back utf8
encoded username in the response header in order to enable support for
non-ascii usernames.
It can be enabled by setting the
"network.auth.digest-response-header-username-utf8" flag to true in the FF
config (about:config).

the patch could be improved by using the charset parameter as defined in RFC
2831, even if the flag is not set. I can probably do if it is asked.

-- 
Configure bugmail: https://bugzilla.mozilla.org/userprefs.cgi?tab=email

-------------------------------
Product/Component: Core :: Networking: HTTP

------- Tracking Flags: -------
blocking2.0:-

------- You are receiving this mail because: -------
You are on the CC list for the bug.