> So: will anon http svn access happen?

I'm late to this round of the discussion, but +1.  I would suggest
https, though, to make it firewall-friendly.  

Even if this is an anonymous mirror (sounds more likely), it would make
sense for community bundle builders (e.g. Plone bundles) to use https
URLs for everything, which supposes upstream can provide https.

Neither http, svnserve, or svn+ssh are friendly to corporate firewalls -
only https (where the firewall can't see the http method verbs because
they are inside a TLS session).  I've griped about this before:

Today, I have to put in requests to my company network admins to open up
to svn.zope.org:3690 out on a workstation by workstation basis.  Their
firewall can do a generic TCP socket proxy (network security folks want
to run an app-level proxy, so we can only set this up one source IP at a
time), and doesn't deal with DeltaV DAV verbs over plain-old http - so
https is the only reasonable option for anonymous checkouts.


 Sean Upton                              SignOnSanDiego.com
 Site Technology Supervisor     The San Diego Union-Tribune
 619.718.5241                 [EMAIL PROTECTED]
 350 Camino De La Reina                 San Diego, CA 92108

  Plone Powered!  plone.org  ++  python.org  ++  zope.org  
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to