Re: Client Option for Strong References

• From: Roy T. Fielding <fielding@kiwi.ics.uci.edu>
• Date: Fri, 09 Oct 1998 18:18:59 -0700
• To: John Stracke <francis@netscape.com>
• cc: "'WebDAV'" <w3c-dist-auth@w3.org>
• Message-ID: <9810091819.aa01477@paris.ics.uci.edu>

>I'm not sure that's the case.  If a client PUTs to a direct reference that it
>thinks is a nonexistent resource, the results can be surprising.  Consider
>this scenario: I have a dangling direct reference into another user's
>directory tree; I don't have write permission on the target.  I come along and
>find that my direct reference is reporting 404; I forget that it was a
>reference, so I think I must have deleted that page.  So I find/create a
>replacement for that page and try to PUT it, only to be told I don't have
>write permission.

I have no problem with that scenario.  The user will figure out what the
problem is as soon as they investigate the cause of the 403, which is
exactly what happens today with non-WebDAV references.  If they want more
done for them automatically, they need to use a PUT tool that understands
WebDAV direct references.

....Roy

Received on Friday, 9 October 1998 21:24:25 UTC