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

Shane Hathaway wrote:
> Martin Aspeli wrote:
>>> Can anyone explain why that condition is there? Otherwise, I'll rip it 
>>> out. ;-)
> 
> As I recall, this code is convoluted because it's hard to tell whether 
> an HTTP request is a WebDAV request.  If there is now a way to clearly 
> distinguish WebDAV requests, then I imagine this code can be greatly 
> simplified.  This code had to deal with Windows 95 and such.

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.


[1] http://www.iana.org/assignments/port-numbers



Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tsea...@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

iEYEARECAAYFAkrL/RIACgkQ+gerLs4ltQ51eQCghdRrMOwwIGOGtRIcwzPPRsii
pW0AnRe6XOLt9K1epcgJLbaG9C9zZGZX
=P+Ba
-----END PGP SIGNATURE-----

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to