   From: Jim Whitehead <ejw@soe.ucsc.edu> Date: Thu, 27 Oct 2005
17:34:39 -0700 Message-Id:
<EEF622B6-064A-4EC9-8C6C-548AD9734197@cs.ucsc.edu> To: Julian
Reschke <julian.reschke@gmx.de>   Julian writes:  > So this is a
process issue -- if it's supposed to become part of   > WebDAV,
it has to make it through the process of (1) define what   > the
problem is, then (2) find a WG consensus of how to resolve   >
this. "Force-Authenticate" may very well be the solution.  OK, I
feel pretty strongly about this feature, so let me do the due
diligence here.   Some WebDAV servers are configured to allow
live authoring, where the   authored changes are immediately
visible to the external world. In   this situation, resources
typically have access controls set such   that GET, HEAD, POST,
PROPFIND and OPTIONS can be performed by any   user without
authentication. Write operations such as PUT, LOCK,   UNLOCK,
MKCOL, MOVE, and COPY require authentication and access
permissions. In some cases, a client would do a series