> -----Original Message-----
> From: Stefan Sperling [mailto:s...@elego.de]
> Sent: maandag 30 mei 2011 16:24
> To: Dimstar / Dominique Leuenberger
> Cc: dev@subversion.apache.org
> Subject: Re: [bug 3740] Change of default behaviour
>
> On Mon, May 30, 2011 at 03:22:57PM +0200, Dimstar / Dominique
> Leuenberger wrote:
> > Now of course I do understand that this patch does bring a change in the
> > default behavior of svn: so far, we simply ignored system settings and
> > let the user crawl through a documentation, finding on how to enable the
> > proxy (based on the number of blog posts on how to do this, it might be
> > a bit hidden, but that's another topic).
>
> For the record I would prefer an expanded patch that adds a new
> configuration option SVN_CONFIG_OPTION_HTTP_USE_SYSTEM_PROXY
> that
> enables this behaviour. I don't think we should change the default
> (no proxy) to use the system proxy settings because Subversion
> is not compatible with every HTTP proxy (notably squid is often
> reported to cause problems). If we start using system proxies by default
> in 1.7 many users might suddently run into issues that didn't exist
> for them before the update. They would perceive this as a regression.
The Squid problem is (if I remember correctly) a serf issue and this patch
is neon specific.
I think we should implement this support for both ra dav layers, while
keeping our normal per server overrides working.
>
> > I for one though would argue that we're just fixing a long standing bug,
> > by finally not ignoring the system anymore. Making the day-to-day life
> > easier.
>
> You would only have to set the new option once in the client config file
> and from then on Subversion will always follow your system proxy settings.
Once this works correctly I would prefer using the system proxy by default.
If you could connect directly, you wouldn't have a system wide proxy
configured. And off by default makes it hard on users to switch to the
system default proxy while still keeping overrides.
Bert
