[Zope-dev] Zope 2 WebDAV and acquisition

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Aspeli wrote:
> Tres Seaver <tseaver <at> palladion.com> writes:
> 
>> There is no way to tell the difference between a WebDAV GET and a
>> "normal" browser GET, period:  the specs explicitly, deliberately
>> overload the GET verb.
>>
>> Hence the IANA-assigned "WebDAV source port"[1] (9800) (which *we*
>> requested) in order to disambiguate those requests.
> 
> Heh, nice.
> 
> Unfortuantely, there's no way to guarantee people will only use this port for
> Zope's WebDAV server.
> 
> That said, the two problems (WebDAV requests result in a browserDefault lookup,
> and folder contents) are not really an issue in everyday use for GET request.
> They merely cause things to explode on PUT requests to a null resource. We *can*
> identify PUT requests, obviously.

Strictly, PUT is not WebDAV-specific;  however, it might be reasonable
to apply the policy you are requesting for any PUT.

> So any comments on my proposal to skip the browserDefault lookup and the
> acquisition of resources for PUT/PROPFIND/PROPPATCH requests?

+.5, I guess.  I'd like to make sure that we aren't breaking some other
use first.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrObj0ACgkQ+gerLs4ltQ7LdwCfY9lYC0JWbWKLhWyzFLVmUDKi
UkwAnjlqpIYZvEu+UiAsC6kM3fU+yEXW
=K0kT
-----END PGP SIGNATURE-----