[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: tortoisesvn browser vs win repo browser

From: MM <finjulhich_at_gmail.com>
Date: Tue, 31 Jan 2012 14:48:16 -0000

> -----Original Message-----
> From: Johan Corveleyn [mailto:jcorvel_at_gmail.com]
> Sent: 31 January 2012 14:05
> To: MM
> Cc: users_at_subversion.apache.org; Ryan Schmidt
> Subject: Re: tortoisesvn browser vs win repo browser
>
> On Tue, Jan 31, 2012 at 2:47 PM, Ryan Schmidt
> <subversion-2012a_at_ryandesign.com> wrote:
> >
> > On Jan 31, 2012, at 07:40, MM wrote:
> >
> >> I have a svn server configured with https.
> >> I managed to browse the repo from a web browser (chrome) where it
> did ask me
> >> for auth username and passwd.
> >> However, using the exact same https://ipaddress as I used in the
> browser,
> >> win repo browser of tortoisesvn fails saying "OPTIONS of
> https://ipaddress
> >> could not connect to server.
> >>
> >> The tortoisesvn repo browser has worked from another IP area.
> >
> > When you browse a repository in a web browser, only GET requests get
> sent. But when you use a real Subversion client, like TortoiseSVN, it
> uses other WebDAV methods, including OPTIONS. What you're seeing could
> be the result of a proxy that's not configured to pass WebDAV methods.
> Try disabling the use of the proxy, or if that's not possible, talk to
> your proxy administrator about supporting WebDAV methods.
> >
>
> I'm also thinking "proxy server". Your browser may have a proxy server
> configured, but for use with any svn client (including TortoiseSVN),
> you have to configure the proxy server in the client-side config file
> (the file "servers" in %APPDATA%/Subversion). Or for TortoiseSVN: just
> open the Settings, and go to "Network".
>
> --
> Johan

This worked, thanks very much,

MM
Received on 2012-01-31 15:47:48 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.