Re: #78: Relationship between 401, Authorization and WWW-Authenticate

Adrien de Croy <adrien@qbik.com> Mon, 25 July 2011 07:38 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 520FE21F8B00 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 25 Jul 2011 00:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.549
X-Spam-Level:
X-Spam-Status: No, score=-10.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cViRwIw3EUHR for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 25 Jul 2011 00:37:59 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id C61C421F850E for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 25 Jul 2011 00:37:59 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1QlFjb-0004nH-Ab for ietf-http-wg-dist@listhub.w3.org; Mon, 25 Jul 2011 07:37:51 +0000
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <adrien@qbik.com>) id 1QlFjT-0004mT-RE for ietf-http-wg@listhub.w3.org; Mon, 25 Jul 2011 07:37:43 +0000
Received: from smtp.qbik.com ([210.55.214.35]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <adrien@qbik.com>) id 1QlFjS-0004op-0V for ietf-http-wg@w3.org; Mon, 25 Jul 2011 07:37:43 +0000
Received: From [192.168.1.10] (unverified [122.57.152.217]) by SMTP Server [210.55.214.35] (WinGate SMTP Receiver v7.0.0 (Build 3259)) with SMTP id <0018406713@smtp.qbik.com>; Mon, 25 Jul 2011 07:37:15 +1200
Message-ID: <4E2D1D1F.7000707@qbik.com>
Date: Mon, 25 Jul 2011 19:37:03 +1200
From: Adrien de Croy <adrien@qbik.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110714 Thunderbird/6.0
MIME-Version: 1.0
To: Willy Tarreau <w@1wt.eu>
CC: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
References: <798C1D1A-C0C7-40DD-8993-31DB735A4961@mnot.net> <20110724181138.GW22405@1wt.eu> <CFBF6FC4-5E17-40A5-A10F-FDCB8B053BAF@mnot.net> <4E2CC6FA.3020207@qbik.com> <20110725044046.GM22405@1wt.eu>
In-Reply-To: <20110725044046.GM22405@1wt.eu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass client-ip=210.55.214.35; envelope-from=adrien@qbik.com; helo=smtp.qbik.com
X-W3C-Hub-Spam-Status: No, score=-3.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RP_MATCHES_RCVD=-1.191, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1QlFjS-0004op-0V 31ad5c0d561e7e9fbfee38b7c65f9ae7
X-Original-To: ietf-http-wg@w3.org
Subject: Re: #78: Relationship between 401, Authorization and WWW-Authenticate
Archived-At: <http://www.w3.org/mid/4E2D1D1F.7000707@qbik.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/11073
X-Loop: ietf-http-wg@w3.org
Sender: ietf-http-wg-request@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Resent-Message-Id: <E1QlFjb-0004nH-Ab@frink.w3.org>
Resent-Date: Mon, 25 Jul 2011 07:37:51 +0000

On 25/07/2011 4:40 p.m., Willy Tarreau wrote:
> On Mon, Jul 25, 2011 at 01:29:30PM +1200, Adrien de Croy wrote:
>>>>> 1) Clarify that WWW-Authenticate can appear on any response, and that
>>>>> when it appears on any other than a 401, it means that the client can
>>>>> optionally present the request again with a credential.
>>>> Does this mean it's only for other 4xx or for any status ? It might have
>>>> implications with non-idempotent requests if a client can repost a request
>>>> that led to a 200 for instance.
>>> Any status. Good point about non-idempotent requests; we'll need to make
>>> clear it's not about automatically retrying requests, but instead that
>>> sending the same request with credentials might have a different affect.
>> isn't this redundant?
>>
>> I see requests with credentials all the time, when no previous
>> WWW-Authorize had been sent in any response.
> Normally they're doing this when they have seen once a 401 with
> WWW-Authenticate. Here the idea is that the server might present
> the header on something different from the 401 (eg: here is your
> data, but if you authenticate I could probably serve something
> more specific to you).

actually we mostly see it when the client agent is a script, downstream 
proxy, tunneling (non-http) client or other non-browser.

They send the header from request #1.

Of course this ignores the issue about whether the method chosen is 
supported / advertised.  Normally it's Basic as well.

Adrien


>
> Regards,
> Willy
>
>

-- 
Adrien de Croy - WinGate Proxy Server - http://www.wingate.com