Correct.
But I need the client on the server for a post-commit-hook. There are some informations retrieved over https by the svn client. And this does not work with serf 1.2.1
And it is perhaps not the performance of apache but of svn.
I have a test repository with the same content over the past 8 years. Before and after each change of a configuration I measure the time consumed for checking out this repository.
The old configuration with Apache 2.2 and SVN 1.8.5 needed 22 seconds.
With Apache 2.4 it lasts about 180 seconds.
Now I fetched SVN binaries from
http://sourceforge.net/projects/win32svn/files/1.8.11/apache24/svn-win32-1.8.11-ap24.zip . These are compiled with VC6. It seems they are working with apache 2.4 VC11 from AH.
Now the problem with certifiacates is gone.
But the checking out is as slow as before. So serf is not the reason for the bad performance.
Then I fetched SVN binaries from
http://sourceforge.net/projects/win32svn/files/1.8.11/apache24/svn-win32-1.8.11-ap22.zip and put them in the Apache 2.2
Nothing changed to the test before. Time to check out 22 seconds.
So the difference is between Apache 2.4 and Apache 2.2?
The configuration is the same. Only the neccesary syntax changes where made.
Or does anybody have an idea for these differences?