Return-Path: 
 <httpclient-user-return-1518-apmail-jakarta-httpclient-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-httpclient-user-archive@www.apache.org
Received: (qmail 75493 invoked from network); 20 Nov 2005 12:10:28 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 20 Nov 2005 12:10:28 -0000
Received: (qmail 24364 invoked by uid 500); 20 Nov 2005 12:10:27 -0000
Delivered-To: apmail-jakarta-httpclient-user-archive@jakarta.apache.org
Received: (qmail 24145 invoked by uid 500); 20 Nov 2005 12:10:23 -0000
Mailing-List: contact httpclient-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:httpclient-user-help@jakarta.apache.org>
List-Unsubscribe: <mailto:httpclient-user-unsubscribe@jakarta.apache.org>
List-Post: <mailto:httpclient-user@jakarta.apache.org>
List-Id: "HttpClient User Discussion" <httpclient-user.jakarta.apache.org>
Reply-To: "HttpClient User Discussion" <httpclient-user@jakarta.apache.org>
Delivered-To: mailing list httpclient-user@jakarta.apache.org
Received: (qmail 24134 invoked by uid 99); 20 Nov 2005 12:10:22 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Nov 2005 04:10:22 -0800
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [195.186.19.62] (HELO mail14.bluewin.ch) (195.186.19.62)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Nov 2005 04:11:55 -0800
Received: from [192.168.0.4] (83.76.13.98) by mail14.bluewin.ch (Bluewin
 7.2.068.1)
        id 435DFE560033617E for httpclient-user@jakarta.apache.org;
 Sun, 20 Nov 2005 12:10:00 +0000
Subject: Re: Problems accessing MapPoint web service after upgrading to 3.0
	RC4
From: Oleg Kalnichevski <olegk@apache.org>
To: HttpClient User Discussion <httpclient-user@jakarta.apache.org>
In-Reply-To: <25aac9fc0511191050v4f3c4065v@mail.gmail.com>
References: <437E00DF.4090506@t-fs.de>
	 <1132351312.2714.5.camel@localhost.localdomain> <437EFD66.80305@t-fs.de>
	 <1132409389.2714.40.camel@localhost.localdomain>
	 <25aac9fc0511190744w3bf2cc69m@mail.gmail.com>
	 <1132421597.2714.57.camel@localhost.localdomain>
	 <25aac9fc0511191016v194f791eu@mail.gmail.com>
	 <1132424823.2714.63.camel@localhost.localdomain>
	 <25aac9fc0511191050v4f3c4065v@mail.gmail.com>
Content-Type: text/plain
Date: Sun, 20 Nov 2005 13:09:59 +0100
Message-Id: <1132488599.2852.12.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) 
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On Sat, 2005-11-19 at 18:50 +0000, sebb wrote:
> > I respectfully disagree. In the HTTP spec quote marks are always
> > designated as <">. See request-digest in the example above
> 
> I can't find qop-value defined anywhere as a quoted string, but nor
> can I find it defined as a non-quoted string.
> 
> But why does the RFC use the unq() function on qop-value unless it is
> a quoted string?
> 
> There are some other examples of the use of unq() - e.g. realm-value -
> in each case all of the operands are defined as being quoted strings.
> 

All right. This is how it goes

qop-value is defined as: 

       qop-value      = "auth" | "auth-int" | token

token is defined as:

       token          = 1*<any CHAR except CTLs or separators>
       separators     = "(" | ")" | "<" | ">" | "@"
                      | "," | ";" | ":" | "\" | <">
                      | "/" | "[" | "]" | "?" | "="
                      | "{" | "}" | SP | HT

in fact qop-value per this definition MAY NOT be a quoted string.

This is an example of digest challenge/response given in the spec, section 3.5 [1]

<quote>

         HTTP/1.1 401 Unauthorized
         WWW-Authenticate: Digest
                 realm="testrealm@host.com",
                 qop="auth,auth-int",
                 nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",
                 opaque="5ccc069c403ebaf9f0171e9517f40e41"

...

         Authorization: Digest username="Mufasa",
                 realm="testrealm@host.com",
                 nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",
                 uri="/dir/index.html",
                 qop=auth,
                 nc=00000001,
                 cnonce="0a4f113b",
                 response="6629fae49393a05397450978507c4ef1",
                 opaque="5ccc069c403ebaf9f0171e9517f40e41"
</quote>

Note qop attribute in the digest response is not quoted, which makes
perfect sense given its definition in the RFC.

Quoted string is defined in the HTTP spec as [2]:

       quoted-string  = ( <"> *(qdtext | quoted-pair ) <"> )
       qdtext         = <any TEXT except <">>
       quoted-pair    = "\" CHAR

Hope this makes things clearer

Cheers,

Oleg

[1] http://www.faqs.org/rfcs/rfc2617.html
[2] http://www.faqs.org/rfcs/rfc2616.html


---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-user-help@jakarta.apache.org