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

Re: Apache wedging over https

From: Neil Bird <neil_at_jibbyjobby.co.uk>
Date: Thu, 27 Jan 2011 13:39:18 +0000

Around about 27/01/11 12:46, Nico Kadel-Garcia typed ...
> I've not seen this, but I'm using Linux, not Solaris, as a server. Are
> you using the Sun provided Apache? Or your own? And is it the built-in
> mod_dav_svn module, or are you doing something else? What's in your
> Apache logs?

   No, I've never seen this before, but then I've also only ever run t under
Linux. Solaris wasn't my choice here, it was IT's. They got the packages
from a site called sunfreeware.com, I believe.

   I see *nothing* in the error logs either when this occurs or when it is
freed. I've not bothered to trace through all of the access logs, as I
imagine there'll be quite a bit of that.

> All HTTPS access is normally set up as a "virtual host" in Apache,
> specific to the HTTPS port, and with the Subversion services set up to
> a particular<Location> in the configuration files. But the setups can
> vary a *lot*. Perhaps you could post your relevant httpd.conf or
> conf.d/svn.conf files for review?

   I largely copied the svn config. location stuff from my working Linux
testbed (itself a modified version of my home setup, so I'm happy with that).

   The SSL's set up in what I presume is normal:

<VirtualHost *:443>

# General setup for the virtual host
DocumentRoot "/usr/local/apache2/htdocs"
ServerName xxx
ServerAdmin xxx
ErrorLog "/usr/local/apache2/logs/error_log"
TransferLog "/usr/local/apache2/logs/access_log"

   Ah, hang on. I wonder if it's because it's pointing the SSL logs at the
same files as the HTTP versions? It's something to try ...

-- 
[neil_at_fnx ~]# rm -f .signature
[neil_at_fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil_at_fnx ~]# exit
Received on 2011-01-27 14:40:01 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.