discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Problem in SVN using Cygwin.


From: Pascal Charest
Subject: Re: [Discuss-gnuradio] Problem in SVN using Cygwin.
Date: Mon, 2 Oct 2006 14:46:23 -0400

I had a similar problem and this is the solution that I used.

At work, my computer is behind a firewall and I must use a proxy server to send HTTP requests. So, I needed to set proxy name and address for SVN. So, edit ~/.subversion/servers. In the [global] section, use these lines:
[global]
http-proxy-host = your.server.address
http-proxy-port = your_server_port

Regards,

Pascal


On 9/29/06, Johnathan Corgan <address@hidden > wrote:
William Guthrie wrote:

> I am glad this thread was ongoing, because I ran into this error too, and it
> helped to know someone else was experiencing it. The problem appears to be our
> corporate firewall. Is there a generic way to get svn to do a checkout around
> a firewall? In the meantime I found I can checkout from home.

I just realized what the issue is when I read your post.

Subversion does indeed use HTTP as the protocol to communicate between a
client and repository server.  However, it uses the WebDAV methods over
HTTP to implement versioning, transactions, etc.  So while typical web
browsing uses HTTP GET and HTTP POST methods, Subversion also uses HTTP
PROPFIND, HTTP MKACTIVITY, and several other WebDAV methods.

Most corporate firewalls (or more likely, transparent proxies) are not
configured to pass or proxy these less frequently used (but still
standard) HTTP methods.

This results in being able to put the URL in your browser and being able
to see the latest version come up, but having Subversion error out when
it doesn't get responses to its queries.

One way around this is to use SSL via a https: URL.  Here, all the HTTP
protocol stuff is necessarily passed through the gateway unchanged (it's
encrypted in the tunnel so the gateway can't "know" what it is.)  It's
just like going to your bank's online web interface.

But this requires configuration on the server end to support, and
gnuradio.org is not set up that way.  It burns a significant amount of
CPU power (for the encryption) and we'd have to evaluate whether our
setup is sufficient to handle the load.

In the short term you can try to convince the powers that be in your
company to enable "WebDAV methods" in their web proxy or firewall.

Johnathan Corgan
address@hidden


_______________________________________________
Discuss-gnuradio mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


reply via email to

[Prev in Thread] Current Thread [Next in Thread]