> From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
>
> Perhaps the whole question of proxy detection belongs in APR?
>
Well, by default I'd think it should all be neon's problem, because it
is our http connection library. Of course, we all know how handy having
neon use APR would be. :) However, sticking the code into APR is
certainly likely to get it more exposure, which isn't the worst thing on
the planet.
> I know that sounds odd, but it seems like proxy setting is highly
> platform- and tradition-specific, which is something APR should deal
> with, not Subversion nor probably Neon.
>
> Should there just be an apr_get_http_proxy() interface?
>
In a perfect world, neon would auto-magically take proxy info into
account and just make it happen.
(Just to make life annoying, IE proxy info even gives you exclusion
patterns to the proxy info, so you have to decide when is appropriate to
actually use the proxy server, etc...)
This (proxy exclusions) makes sense for SVN anyway. You have to support
accessing live internet repositories outside the proxy, and
simultaneously not make life too annoying for the folks who need to
access intranet repositories at the same time.
The easiest way in the short run is to just stick some proxy config info
into .svnrc.
e.g.:
Default proxy config settings
Per Repository overrides for config settings
Etc...
NTLM authenticating proxies:
If you're using Microsoft's proxy server this isn't an issue on Win32
boxes, because they'll have the Winsock proxy client installed.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:53 2006