Svn will not remember passphrase for client certificate.

2016-04-12 Thread Chris Capon
Subversion v1.9.3, Apache2 v2.4.18 Our subversion server uses SSL with client certificates. When performing any action against the repository using the svn client, a prompt appears asking for the password to the client certificate. (Note: this is not the user id / password combination). Expecte

Re: Unexpected HTTP status 400 'Bad request'.

2015-12-11 Thread Chris Capon
On 2015-12-08 11:16, Stefan Sperling wrote: please try raising HTTPD's LogLevel to "Debug" or higher. See http://httpd.apache.org/docs/2.4/mod/core.html#loglevel Perhaps that will shed more light on the problem. Hi All. I appreciate the time you guys are taking to help me. Thank you. Here i

Re: Unexpected HTTP status 400 'Bad request'.

2015-12-08 Thread Chris Capon
On 2015-12-08 09:09, Bert Huijben wrote: Are you using some kind of (caching) proxy server when you connect to the server? You are focusing your search to a disk problem (probably caused by hints on this list), while you are trying to determine what causes a 'bad HTTP request' error. Bad reques

Re: Unexpected HTTP status 400 'Bad request'.

2015-12-08 Thread Chris Capon
Hi Bert. The only log I know of is under /var/log/apache2/subversion.log, and when I issue a checkout, I get only two lines in it: [08/Dec/2015:09:24:53 -500] myself get-inherited-props /dev/trunk r3066 [08/Dec/2015:09:24:53 -500] myself checkout-or-export /dev/trunk r3066 If the error were

Re: Unexpected HTTP status 400 'Bad request'.

2015-12-08 Thread Chris Capon
I Added both these lines to the section of the Apache2 configuration file. When I do an svn checkout locally, I get the same error occurring. On 2015-12-08 06:09, Yves Martin wrote: Hello, In my Apache2 configuration, I have added "LimitRequestBody 0" and "LimitXMLRequestBody 0" to avoid

Re: Unexpected HTTP status 400 'Bad request'.

2015-12-08 Thread Chris Capon
p.s. The server is around 8 years old and has been maintained and regularly updated, pinned to the Testing release of Debian. On 2015-12-08 05:06, Yves Martin wrote: I guess your repository has been created long ago with a previous version of Subversion.

Re: Unexpected HTTP status 400 'Bad request'.

2015-12-08 Thread Chris Capon
On 2015-12-08 05:06, Yves Martin wrote: Hello​ Is your repository served read-write by other services like svnserve or eventually through SSH in addition to Apache HTTPS access ? I'm sorry. I don't understand what this asks. Permissions are controlled by a .apache_auth and .apache_htpasswd

Re: Unexpected HTTP status 400 'Bad request'.

2015-12-08 Thread Chris Capon
re of a clue about what is going wrong. Eric. On Mon, Dec 7, 2015 at 10:13 PM, Chris Capon <mailto:ttab...@gmail.com>> wrote:

Re: Unexpected HTTP status 400 'Bad request'.

2015-12-07 Thread Chris Capon
On 2015-12-07 20:48, David Chapman wrote: Have you verified that the repository on the server is not corrupt? Perhaps the disk has a bad sector on the drive, and only that repository is affected. Or maybe the hard drive itself is failing, and the other repositories have simply been "lucky" s

Unexpected HTTP status 400 'Bad request'.

2015-12-07 Thread Chris Capon
Hi. We are running a Subversion server using Apache2 2.4.17-3, modDAV, and Subversion 1.9.2-3+b1 (the latest Testing release) under Debian GNU/Linux. We use HTTPS for security along with client certificates. This server has been running for many years with the same configuration. A week or