svn over HTTP proxy

Question

I m on laptop  Ubuntu  with a network that use HTTP proxy  only http connections allowed   When I use svn up for url like  http          everything is cool  google chrome repository works perfect   but right now I need to svn up from server with  svn         and I see connection refused  I ve set proxy configuration in  etc subversion servers but it doesn t help  Anyone have opinion solution

User · Answer

svn    doesn t talk http  therefor there s nothing a http proxy could do   Any reason why http doesn t work  Have you considered https  If you really need it  you probably have to have port 3690 opened in your firewall

User · Answer

when you use the svn    URI it uses port 3690 and probably won t use http proxy

User · Answer

In  etc subversion servers you are setting http-proxy-host  which has nothing to do with svn    which connects to a different server usually running on port 3690 started by  svnserve command   If you have access to the server  you can setup svn ssh    as explained here   Update  You could also try using connect-tunnel  which uses your HTTPS proxy server to tunnel connections   connect-tunnel -P proxy company com 8080 -T 10234 svn example com 3690   Then you would use  svn checkout svn   localhost 10234 path to trunk

User · Answer

In  etc subversion servers you are setting http-proxy-host  which has nothing to do with svn    which connects to a different server usually running on port 3690 started by  svnserve command   If you have access to the server  you can setup svn ssh    as explained here   Update  You could also try using connect-tunnel  which uses your HTTPS proxy server to tunnel connections   connect-tunnel -P proxy company com 8080 -T 10234 svn example com 3690   Then you would use  svn checkout svn   localhost 10234 path to trunk

User · Answer

If you can get SSH to it you can an SSH Port-forwarded SVN server    Use SSHs -L   or -R   I forget  it always confuses me   to make an ssh tunnel  so that   127 0 0 1 3690  is really connecting to remote 3690 over the ssh tunnel  and then you can use it via   svn co svn   127 0 0 1

User · Answer

In  etc subversion servers you are setting http-proxy-host  which has nothing to do with svn    which connects to a different server usually running on port 3690 started by  svnserve command   If you have access to the server  you can setup svn ssh    as explained here   Update  You could also try using connect-tunnel  which uses your HTTPS proxy server to tunnel connections   connect-tunnel -P proxy company com 8080 -T 10234 svn example com 3690   Then you would use  svn checkout svn   localhost 10234 path to trunk

User · Answer

svn    doesn t talk http  therefor there s nothing a http proxy could do   Any reason why http doesn t work  Have you considered https  If you really need it  you probably have to have port 3690 opened in your firewall

User · Answer

If you can get SSH to it you can an SSH Port-forwarded SVN server    Use SSHs -L   or -R   I forget  it always confuses me   to make an ssh tunnel  so that   127 0 0 1 3690  is really connecting to remote 3690 over the ssh tunnel  and then you can use it via   svn co svn   127 0 0 1

User · Answer

If you re using the standard SVN installation the svn    connection will work on tcpip port 3690 and so it s basically impossible to connect unless you change your network configuration  you said only Http traffic is allowed  or you install the http module and Apache on the server hosting your SVN server

User · Answer

Okay  this topic is somewhat outdated  but as I found it on google and have a solution this might be interesting for someone   Basically  of course  this is not possible on every http proxy but works on proxies allowing http connect on port 3690  This method is used by http proxies on port 443 to provide a way for secure https connections  If your administrator configures the proxy to open port 3690 for http connect you can setup your local machine to establish a tunnel through the proxy   I just was in the need to check out some files from svn openwrt org within our companies network  An easy solution to create a tunnel is adding the following line to your  etc hosts  127 0 0 1 svn openwrt org  Afterwards  you can use socat to create a tcp tunnel to a local port   while true  do socat tcp-listen 3690 proxy proxy at your company svn openwrt org 3690  done  You should execute the command as root  It opens the local port 3690 and on connection creates a tunnel to svn openwrt org on the same port   Just replace the port and server addresses on your own needs

User · Answer

If you re using the standard SVN installation the svn    connection will work on tcpip port 3690 and so it s basically impossible to connect unless you change your network configuration  you said only Http traffic is allowed  or you install the http module and Apache on the server hosting your SVN server

User · Answer

when you use the svn    URI it uses port 3690 and probably won t use http proxy

User · Answer

If you can get SSH to it you can an SSH Port-forwarded SVN server    Use SSHs -L   or -R   I forget  it always confuses me   to make an ssh tunnel  so that   127 0 0 1 3690  is really connecting to remote 3690 over the ssh tunnel  and then you can use it via   svn co svn   127 0 0 1

User · Answer

Okay  this topic is somewhat outdated  but as I found it on google and have a solution this might be interesting for someone   Basically  of course  this is not possible on every http proxy but works on proxies allowing http connect on port 3690  This method is used by http proxies on port 443 to provide a way for secure https connections  If your administrator configures the proxy to open port 3690 for http connect you can setup your local machine to establish a tunnel through the proxy   I just was in the need to check out some files from svn openwrt org within our companies network  An easy solution to create a tunnel is adding the following line to your  etc hosts  127 0 0 1 svn openwrt org  Afterwards  you can use socat to create a tcp tunnel to a local port   while true  do socat tcp-listen 3690 proxy proxy at your company svn openwrt org 3690  done  You should execute the command as root  It opens the local port 3690 and on connection creates a tunnel to svn openwrt org on the same port   Just replace the port and server addresses on your own needs

User · Answer

Ok  this should be really easy     sudo vi  etc subversion servers   Edit the file    Global  http-proxy-host my proxy com http-proxy-port 3128   Save it  run svn again and it will work

User · Answer

If you can get SSH to it you can an SSH Port-forwarded SVN server    Use SSHs -L   or -R   I forget  it always confuses me   to make an ssh tunnel  so that   127 0 0 1 3690  is really connecting to remote 3690 over the ssh tunnel  and then you can use it via   svn co svn   127 0 0 1

User · Answer

If you re using the standard SVN installation the svn    connection will work on tcpip port 3690 and so it s basically impossible to connect unless you change your network configuration  you said only Http traffic is allowed  or you install the http module and Apache on the server hosting your SVN server

User · Answer

In  etc subversion servers you are setting http-proxy-host  which has nothing to do with svn    which connects to a different server usually running on port 3690 started by  svnserve command   If you have access to the server  you can setup svn ssh    as explained here   Update  You could also try using connect-tunnel  which uses your HTTPS proxy server to tunnel connections   connect-tunnel -P proxy company com 8080 -T 10234 svn example com 3690   Then you would use  svn checkout svn   localhost 10234 path to trunk

User · Answer

when you use the svn    URI it uses port 3690 and probably won t use http proxy

User · Answer

If you re using the standard SVN installation the svn    connection will work on tcpip port 3690 and so it s basically impossible to connect unless you change your network configuration  you said only Http traffic is allowed  or you install the http module and Apache on the server hosting your SVN server

User · Answer

In  etc subversion servers you are setting http-proxy-host  which has nothing to do with svn    which connects to a different server usually running on port 3690 started by  svnserve command   If you have access to the server  you can setup svn ssh    as explained here   Update  You could also try using connect-tunnel  which uses your HTTPS proxy server to tunnel connections   connect-tunnel -P proxy company com 8080 -T 10234 svn example com 3690   Then you would use  svn checkout svn   localhost 10234 path to trunk

User · Answer

when you use the svn    URI it uses port 3690 and probably won t use http proxy

User · Answer

If you re using the standard SVN installation the svn    connection will work on tcpip port 3690 and so it s basically impossible to connect unless you change your network configuration  you said only Http traffic is allowed  or you install the http module and Apache on the server hosting your SVN server

User · Answer

If you can get SSH to it you can an SSH Port-forwarded SVN server    Use SSHs -L   or -R   I forget  it always confuses me   to make an ssh tunnel  so that   127 0 0 1 3690  is really connecting to remote 3690 over the ssh tunnel  and then you can use it via   svn co svn   127 0 0 1

User · Answer

Okay  this topic is somewhat outdated  but as I found it on google and have a solution this might be interesting for someone   Basically  of course  this is not possible on every http proxy but works on proxies allowing http connect on port 3690  This method is used by http proxies on port 443 to provide a way for secure https connections  If your administrator configures the proxy to open port 3690 for http connect you can setup your local machine to establish a tunnel through the proxy   I just was in the need to check out some files from svn openwrt org within our companies network  An easy solution to create a tunnel is adding the following line to your  etc hosts  127 0 0 1 svn openwrt org  Afterwards  you can use socat to create a tcp tunnel to a local port   while true  do socat tcp-listen 3690 proxy proxy at your company svn openwrt org 3690  done  You should execute the command as root  It opens the local port 3690 and on connection creates a tunnel to svn openwrt org on the same port   Just replace the port and server addresses on your own needs

User · Answer

when you use the svn    URI it uses port 3690 and probably won t use http proxy

User · Answer

If you can get SSH to it you can an SSH Port-forwarded SVN server    Use SSHs -L   or -R   I forget  it always confuses me   to make an ssh tunnel  so that   127 0 0 1 3690  is really connecting to remote 3690 over the ssh tunnel  and then you can use it via   svn co svn   127 0 0 1

User · Answer

Okay  this topic is somewhat outdated  but as I found it on google and have a solution this might be interesting for someone   Basically  of course  this is not possible on every http proxy but works on proxies allowing http connect on port 3690  This method is used by http proxies on port 443 to provide a way for secure https connections  If your administrator configures the proxy to open port 3690 for http connect you can setup your local machine to establish a tunnel through the proxy   I just was in the need to check out some files from svn openwrt org within our companies network  An easy solution to create a tunnel is adding the following line to your  etc hosts  127 0 0 1 svn openwrt org  Afterwards  you can use socat to create a tcp tunnel to a local port   while true  do socat tcp-listen 3690 proxy proxy at your company svn openwrt org 3690  done  You should execute the command as root  It opens the local port 3690 and on connection creates a tunnel to svn openwrt org on the same port   Just replace the port and server addresses on your own needs

User · Answer

If you re using the standard SVN installation the svn    connection will work on tcpip port 3690 and so it s basically impossible to connect unless you change your network configuration  you said only Http traffic is allowed  or you install the http module and Apache on the server hosting your SVN server

User · Answer

svn    doesn t talk http  therefor there s nothing a http proxy could do   Any reason why http doesn t work  Have you considered https  If you really need it  you probably have to have port 3690 opened in your firewall

User · Answer

svn    doesn t talk http  therefor there s nothing a http proxy could do   Any reason why http doesn t work  Have you considered https  If you really need it  you probably have to have port 3690 opened in your firewall

User · Answer

svn    doesn t talk http  therefor there s nothing a http proxy could do   Any reason why http doesn t work  Have you considered https  If you really need it  you probably have to have port 3690 opened in your firewall

User · Answer

Ok  this should be really easy     sudo vi  etc subversion servers   Edit the file    Global  http-proxy-host my proxy com http-proxy-port 3128   Save it  run svn again and it will work

User · Answer

In  etc subversion servers you are setting http-proxy-host  which has nothing to do with svn    which connects to a different server usually running on port 3690 started by  svnserve command   If you have access to the server  you can setup svn ssh    as explained here   Update  You could also try using connect-tunnel  which uses your HTTPS proxy server to tunnel connections   connect-tunnel -P proxy company com 8080 -T 10234 svn example com 3690   Then you would use  svn checkout svn   localhost 10234 path to trunk

User · Answer

If you re using the standard SVN installation the svn    connection will work on tcpip port 3690 and so it s basically impossible to connect unless you change your network configuration  you said only Http traffic is allowed  or you install the http module and Apache on the server hosting your SVN server

User · Answer

svn    doesn t talk http  therefor there s nothing a http proxy could do   Any reason why http doesn t work  Have you considered https  If you really need it  you probably have to have port 3690 opened in your firewall

User · Answer

Ok  this should be really easy     sudo vi  etc subversion servers   Edit the file    Global  http-proxy-host my proxy com http-proxy-port 3128   Save it  run svn again and it will work

User · Answer

Ok  this should be really easy     sudo vi  etc subversion servers   Edit the file    Global  http-proxy-host my proxy com http-proxy-port 3128   Save it  run svn again and it will work

User · Answer

svn    doesn t talk http  therefor there s nothing a http proxy could do   Any reason why http doesn t work  Have you considered https  If you really need it  you probably have to have port 3690 opened in your firewall

User · Answer

when you use the svn    URI it uses port 3690 and probably won t use http proxy

User · Answer

when you use the svn    URI it uses port 3690 and probably won t use http proxy

User · Answer

svn    doesn t talk http  therefor there s nothing a http proxy could do   Any reason why http doesn t work  Have you considered https  If you really need it  you probably have to have port 3690 opened in your firewall

User · Answer

In  etc subversion servers you are setting http-proxy-host  which has nothing to do with svn    which connects to a different server usually running on port 3690 started by  svnserve command   If you have access to the server  you can setup svn ssh    as explained here   Update  You could also try using connect-tunnel  which uses your HTTPS proxy server to tunnel connections   connect-tunnel -P proxy company com 8080 -T 10234 svn example com 3690   Then you would use  svn checkout svn   localhost 10234 path to trunk

User · Answer

In  etc subversion servers you are setting http-proxy-host  which has nothing to do with svn    which connects to a different server usually running on port 3690 started by  svnserve command   If you have access to the server  you can setup svn ssh    as explained here   Update  You could also try using connect-tunnel  which uses your HTTPS proxy server to tunnel connections   connect-tunnel -P proxy company com 8080 -T 10234 svn example com 3690   Then you would use  svn checkout svn   localhost 10234 path to trunk

User · Answer

If you can get SSH to it you can an SSH Port-forwarded SVN server    Use SSHs -L   or -R   I forget  it always confuses me   to make an ssh tunnel  so that   127 0 0 1 3690  is really connecting to remote 3690 over the ssh tunnel  and then you can use it via   svn co svn   127 0 0 1

User · Answer

If you re using the standard SVN installation the svn    connection will work on tcpip port 3690 and so it s basically impossible to connect unless you change your network configuration  you said only Http traffic is allowed  or you install the http module and Apache on the server hosting your SVN server

User · Answer

when you use the svn    URI it uses port 3690 and probably won t use http proxy

User · Answer

If you can get SSH to it you can an SSH Port-forwarded SVN server    Use SSHs -L   or -R   I forget  it always confuses me   to make an ssh tunnel  so that   127 0 0 1 3690  is really connecting to remote 3690 over the ssh tunnel  and then you can use it via   svn co svn   127 0 0 1

[linux] svn over HTTP proxy

Examples related to linux

Examples related to svn

Examples related to ubuntu

Examples related to proxy