Re: svn checkout via a web-browser?
On 7/4/07, Karl E. Jorgensen <email@example.com> wrote:
On Wed, Jul 04, 2007 at 10:20:57AM +0200, Tshepang Lekhonkhobe wrote:
> On 7/3/07, Vincent Lefevre <firstname.lastname@example.org> wrote:
> >On 2007-07-03 16:26:40 +0200, Tshepang Lekhonkhobe wrote:
> >> On 7/3/07, Vincent Lefevre <email@example.com> wrote:
> >>> On 2007-07-03 13:40:47 +0200, Tshepang Lekhonkhobe wrote:
> >>> > Me have been struggling to access a subversion repo (svn checkout
> >>> > svn.gnome.org/svn/tracker/trunk) due to being behind a proxy server. I
> >>> > wonder if there's a way to download such repos without having an svn
> >>> > client since I can access the web with a web-browser.
> >>> Only if your web browser is a also svn client. But if it isn't, why
> >>> don't you install a svn client?
> >> I failed: http://lists.debian.org/debian-user/2007/07/msg00075.html
> >> And help didn't help:
> >> http://lists.debian.org/debian-user/2007/07/msg00162.html
> >You'll probably have the same problem with a web browser having a
> >svn client extension. With a proxy server that filters some method,
> >you can't access all the web, and changing the client won't solve
> >your problem. If you control the web server itself, perhaps you can
> >try something like SSH over HTTP (if CONNECT is allowed).
> It's interesting to note that I tried TortoiseSVN which runs on
> Windows and worked without a breeze. This leads me to think that the
> web server (which I dodn't control) does accept svn requests.
> The company network is run by Windows.
I'm getting in late in this thread, but the "windows proxy" thing caught
my eye (or is it "caught my ear"? never mind...)
Most unix/linux tools are quite happy to work behind a standard HTTP
proxy. But windows IIS proxy is *NOT* a standard proxy when it requires
NTLM authentication - weirdy stuff...
But epiphany understands NTLM, and I presume that TortoiseSVN does too.
If you gave them your Windows "active directory" (ldap for you and me)
password, that would be a clue.
If the proxy is an NTLM-demanding windows proxy, then I'd expect other
tools *not* to work too, e.g.:
$ wget http://www.google.com
would fail because of the proxy. Even:
$ http_proxy=http://188.8.131.52:80 wget --proxy-user yourname --proxy-password=yourpassword http://www.google.com
would fail too with a message to the effect "not allowed".
If you *do* have one of these nasty NTLM proxies, you can still use it
by adding your own proxy "in front of" it (which usually means locally)
nd letting your applications use that as a proxy. That's what the
ntlmaps package does...
This is copied from ntlmaps' config file and my inputs:
# If you want APS to authenticate you at WWW servers using NTLM then
just leave this
# value blank like PARENT_PROXY: and APS will connect to web servers directly.
# You can specify more than one proxy by leaving a space between each one, and
# APS will detect when one fails and automatically fail-over to the next. EG:
#PARENT_PROXY:first_proxy second_proxy third_proxy
# And NOTE that NTLM cannot pass through another proxy server.
PARENT_PROXY: 172.16.3.1 184.108.40.206
1st IP is company's proxy server (one I successfully use with
Epiphany) and the 2nd one is my own (and I wonder if this is enough to
create own proxy).
This is copied from wget's config file and my inputs:
http_proxy = http://220.127.116.11:80/
So, running wget x.org times out since it takes forever without
Similarly, adding same own proxy data to ./subversion/servers results
in a forever wait, and failure.
my place on the web: