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

Failure of long commits using dav_svn & SSL

From: Will Wilson <willw_at_fireflyworlds.com>
Date: 2007-06-13 13:02:35 CEST

I have a feeling this isn't an issue with subversion code, but
nonetheless I thought it prudent to highlight the issue and solution in
case anyone else should run into it...

We're running Apache/2.0.55 (Win32) DAV/2 mod_auth_sspi/1.0.4
mod_ssl/2.0.55 OpenSSL/0.9.8a SVN/1.4.3. This has all worked perfectly
with the repositories accessed by https. A while ago some of our remote
developers were finding their commits would fail when committing large
files (60+ MB) to the repository. On the client(s) (TSVN 1.4.x) the
failure would display as:

PUT of '/svn/repos/!svn/wrk/GUID/path': authorization failed
(https://server_name)

In the server logs we saw:

[error] [client x.x.x.x] (OS 87)The parameter is incorrect. :
authentication failure for "/svn/repos/!svn/wrk/GUID/path": user
unknown, reason: cannot generate context
[error] [client x.x.x.x] Provider encountered an error while streaming a
REPORT response. [500, #0]
[error] [client x.x.x.x] A failure occurred while driving the update
report editor [500, #620019]
[error] [client x.x.x.x] Error writing base64 data: APR does not
understand this error code [500, #620019]

It seems that increasing the SSLSessionCacheTimeout parameter "resolves"
the issue. Ours was originally 5 minutes, after increasing it to an hour
the issue disappeared.

Hopefully this will be useful to someone.

Cheers,
        Will.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 13 13:02:58 2007

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