W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2002

Re: Interop issue: how can clients force authentication?

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Wed, 18 Sep 2002 10:35:01 +0200
Cc: Julian Reschke <julian.reschke@gmx.de>, Webdav WG <w3c-dist-auth@w3c.org>
To: Ilya Kirnos <ilya.kirnos@oracle.com>
Message-Id: <85D59A30-CAE1-11D6-9F78-00039384827E@greenbytes.de>


Am Mittwoch den, 18. September 2002, um 03:38, schrieb Ilya Kirnos:

> [...]
>> From what I hear now, you want to authenticate, but not for a specific
>> method call on a specific resource. What is this supposed to 
>> *mean*? What
>> principals are known may depend on the request URI. Whether (and 
>> as who)
>> you need to authenticate to apply a certain method to a resource 
>> depends on
>> the resource *and* the method.
>>
>> In general, the answer -- you'lll have to try.
>>
>
> okay.  this answer is currently not sufficient, for example in the 
> case of a
> large PUT.  whether it's an interop or a performance problem, i 
> believe it's
> something that needs to be addressed.  if there is something 
> already in the spec
> that solves the problem, i would be happy to use it.

Well, as someone (Roy?) mentioned, the Expect header in RFC 2616 servs
that pupose.

//Stefan
Received on Wednesday, 18 September 2002 04:36:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:01 GMT