Johan Corveleyn wrote:
> You could be experiencing a client-side timeout. Svn with neon (which
> is the default client-side http access library) has a default timeout
> of 30 seconds. If the client doesn't get something within those 30
> seconds, it terminates the connection.
>
> You can specify a
Johan Corveleyn wrote:
>> But i did not expect success here, because the error occurred after
>> about 15 minutes what is much longer than the http-timeout.
>
> [ Remember to put the list in cc as well, so the reply goes not only to me ]
Sorry for that.
> Alternatively, in your setup (with squid
On Tue, Mar 9, 2010 at 2:37 PM, Steffen Sledz wrote:
> Johan Corveleyn wrote:
>> You could be experiencing a client-side timeout. Svn with neon (which
>> is the default client-side http access library) has a default timeout
>> of 30 seconds. If the client doesn't get something within those 30
>> s
e to enable a few extra commands.
>
> The squid works fine for a long time on all other requests
> including git-svn on smaller repositories.
>
>>> Provider encountered an error while streaming a REPORT
>>> response. [400, #0]
>>
>> Smells like a proxy/fi
smaller repositories.
>> Provider encountered an error while streaming a REPORT
>> response. [400, #0]
>
> Smells like a proxy/firewall that refuses to let something pass.
H? I don't think so. As mentioned before the procedure
works fine on smaller repos. It looks like a size/timeout
problem.
Steffen
nal error comes from the SVN-Server itself and is this one:
>
> Provider encountered an error while streaming a REPORT
> response. [400, #0]
Smells like a proxy/firewall that refuses to let something pass.
Try
- with plain svn instead of git
- via HTTP instead of HTTP
y timeout comes from a squid transparent proxy which
acts as an auth gatekeeper. The original error comes from the
SVN-Server itself and is this one:
Provider encountered an error while streaming a REPORT response. [400, #0]
Any hints how we can fix the problem?
Steffen
