On Tue, Aug 14, 2012 at 1:10 AM, Philip Martin <philip.mar...@wandisco.com> wrote: > Johan Corveleyn <jcor...@gmail.com> writes: > >> I tried all I can think of for configuring Apache. Pfffff. > > Do you have an explicit ServerName? Are you using VirtualHost? Can you > connect using 1.7/neon? Can you connect using a browser?
Explicit ServerName: yes. Using a VirtualHost: yes, I was, but now I've removed it ... still same problem. 1.7/neon: same error. Browser: yes, no problem (after ignoring the security warnings about the self-signed certificate) > Here is the complete Apache config file generated by davautocheck.sh: For my last attempt I actually made my configuration almost exactly the same as the one in davautocheck.sh. So without a VirtualHost etc. See attachment for my last attempt. I also re-installed Apache (2.2.22 (including openssl 0.9.8t)) from the officially distributed Windows binaries. After all these attempts, I'm wondering if this even works (with Windows clients, because it seems to work for you so I suppose it's Windows specific): being able to accept a self-signed (or signed by untrusted CA) certificate permanently. Maybe some strange quirk somewhere ... ?? However, when I add --non-interactive and --trust-server-cert to the command, it works. No prompt whatsoever. Why doesn't the test-suite actually use those two options to suppress cert-stuff? -- Johan
httpd.conf
Description: Binary data
