On Thu, Sep 4, 2008 at 2:08 AM, Brett Cannon <[EMAIL PROTECTED]> wrote: >> >> And why not to setup HTTPS for anonymous read and authorized write >> access? It is not that hard to do and will solve many problems with >> proxies. > > Because it requires setting up a certificate.
Certificate is already set. $ svn co https://svn.python.org/projects/trunk Error validating server certificate for 'https://svn.python.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: svn.python.org - Valid: from Apr 10 00:00:00 2007 GMT until Apr 9 23:59:59 2010 GMT - Issuer: http://www.usertrust.com, The USERTRUST Network, Salt Lake City, UT, US - Fingerprint: fc:67:c1:59:f5:57:71:29:f5:13:50:bc:c9:16:f1:74:da:1f:12:98 (R)eject, accept (t)emporarily or accept (p)ermanently? t Authentication realm: <https://svn.python.org:443> Subversion repository Password for 'username': Authentication realm: <https://svn.python.org:443> Subversion repository Username: svn: PROPFIND request failed on '/projects/trunk' svn: PROPFIND of '/projects/trunk': authorization failed (https://svn.python.org) > You can use HTTP to do a read-only checkout. Well, the main problem is that I can't. As I already said my machine is behind a proxy that doesn't support required WebDAV extensions for HTTP protocol - http://subversion.tigris.org/faq.html#proxy -- --anatoly t. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
