This happens only on large commit (resulting in a failed commit):
Revelant section from virtual host config in Apache
<LimitExcept GET PROPFIND OPTIONS REPORT> Require valid-user </LimitExcept> Dav svn SVNPath /home/svn/
Commit result:
Transmitting file data ..............................svn: Commit failed (details follow): svn: PUT of '/!svn/wrk/48583f7d-0e01-410d-8941-33d2ba3574b4/WAP/.../htdocs/images/rt.gif': SSL negotiation failed: SSL error: parse tlsext (https://...)
I found references to it here: http://code.google.com/p/support/issues/detail?id=1395
stating that OpenSSL should be compiled with TLS extension, but in my case, it doesn't error out at the start, just on large commits.
Any ideas? Thanks
I haven't experienced this issue, but I spent a while googling around and found that it may have been introduced in Apache 2.2.12 or 13. It is suggested that downgrading to 2.2.11 may fix it, as well as setting SSLProtocol -ALL +SSLv2 +SSLv3 in your Apache config. Neither one seemed definitive. Good luck! Hope you find a solution.
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2393204
UPDATE
After reading the http-dev thread about this issue, archived at http://www.gossamer-threads.com/lists/apache/dev/375633 , it seems this issue is caused by a bug in the client-side OpenSSL library in regards to how SSL Tickets / IDs are handled, which explains why the error does not occur immediately, but takes a few seconds to minutes. This resolution was determined on Nov 2, three days before OpenSSL 0.9.8l came out. The thread does not explicitly state if/when the fix was applied to OpenSSL, but I think it's something we can anticipate being fixed in 0.9.8m, which I believe is covered by this entry in the m-beta changelog:
ORIGINAL POST
I'm experiencing similar issues on Apache-2.2.14 on Gentoo. For reference, here's my USE flags:
This occurs with any combination of SSLProtocol with
TLSv1
includedIf I adjust my
SSLProtocol
to removeTLSv1
, I get a new error:This occurs at approximately the same time that I'd encounter the "parse tlsext" error instead.
This issue is most propably because of using multiple SSL enabled VirtualHosts in Apache httpd 2.2.12 - 2.2.14 and OpenSSL 0.9.8f - 0.9.8l .
The following patch seems to solve the issue for me.