[Zope3-dev] Other (than GET and POST) HTTP Methods

[Tres Seaver]

On Wed, 2003-01-08 at 11:47, Phillip J. Eby wrote:
> At 11:10 AM 1/8/03 -0500, Shane Hathaway wrote:
> >Jim Fulton wrote:
> >>You can't distinguish Browser GETs from WebDAV, Amaya, or Composer GETs.
> >>You can't distinguish WebDAV PUTs from Amaya, or Composer PUTs.
> >
> >That's actually a reason why you'd want to run WebDAV on a different port 
> >from normal HTTP, isn't it?
> 
> No, that's why you want them on the same port.  Transparency.  The whole 
> idea behind PUT in HTTP and WebDAV is that you PUT to the same URL you want 
> to GET from.  So that you can just browse "the site" and edit it in place.
> 
> 
> >In special cases, you *can* distinguish WebDAV from browser GETs (using 
> >user-agent sniffing, IP address sniffing, special URLs, or custom headers),
> 
> *Shudder*  Why would you *want* to?
> 
> IMO, WebDAV is *supposed* to be on the same port.  That's the whole 
> point.  It's an HTTP extension, not a replacement.

GET *cannot* do the Right Thing (tm) for both WebDAV clients and
browsers for "dynamic" content;  *no* DAV client correctly checks the
"document source" property;  they all expect to be able to do a plain
GET on the resource's "main" URL.  The "WebDAV source port" in Zope2
works around this defect (in the clients).

Tres.
-- 
===============================================================
Tres Seaver                                tseaver@zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com