Re: Bug report for tortoiseSVN

On 27.11.2013 21:49, Andrew Klitzke wrote:
> Hi all,
>
> I would like to report what might be a bug.
>
> We use TortoiseSVN every day. It works great, keep up the good work.
> However, we discovered a rather crippling problem when used in certain
> instances.
>
> We connect to a local subversion server for our repository. We use http.
>
> Works great when we’re actually in the network. However, when we VPN
> into our work network, TortoiseSVN versions 1.8+ fail when connecting
> with the error “Unexpected HTTP status 400 ‘Bad Request’ (The HTTP
> request includes a non-supported header. )”

Seems in this situation, you have a proxy in between that's too old to
work with the serf library that svn uses, or a proxy that rejects DAV
requests completely.

> We’ve verified it’s not an issue with the internet configuration on our
> target machines. We are able to connect and view the subversion server
> just fine in our browsers while TortoiseSVN simultaneously fails.

If you use a web browser, you only get plain html. Only if you use an
svn client, then DAV requests have to get through as well.

> In addition, when we downgrade to TortoiseSVN 1.7.*, it works great
> through the VPN.

1.7.x svn clients use the neon library which works as well with very old
proxies. Serf however does not work with proxies that don't implement
the protocols correctly (older proxies don't always follow the
specifications properly, and neon worked around that. Serf can't anymore
but it's also faster).

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3069397
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].