From owner-freebsd-questions@FreeBSD.ORG  Sun Jan 22 19:39:13 2006
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8E4EE16A41F
	for <freebsd-questions@freebsd.org>;
	Sun, 22 Jan 2006 19:39:13 +0000 (GMT)
	(envelope-from brent@academy.netmojo.ca)
Received: from academy.netmojo.ca (academy.pims.math.ca [198.161.29.185])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5C9F143D49
	for <freebsd-questions@freebsd.org>;
	Sun, 22 Jan 2006 19:39:13 +0000 (GMT)
	(envelope-from brent@academy.netmojo.ca)
Received: by academy.netmojo.ca (Postfix, from userid 500)
	id C28C32125F; Sun, 22 Jan 2006 12:40:16 -0700 (MST)
Date: Sun, 22 Jan 2006 12:40:16 -0700
From: Brent Kearney <brent@kearneys.ca>
To: freebsd-questions@freebsd.org
Message-ID: <20060122194016.GB2210@kearneys.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Subject: Apache 2.0.55_2 mod_dav not working
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jan 2006 19:39:13 -0000

Hello,

After upgrading apache from 2.0.54 to the latest version, 2.0.55_2, WebDAV 
has stopped working.  The mod_dav and mod_dav_fs modules load OK, but the 
lock file that is specified in the DavLockDB directive does not get created, 
and WebDAV clients cannot connect.

The /server-info page provided by mod_info shows that the DAV modules are active:

Module Name: mod_dav.c
Content handlers: yes
Configuration Phase Participation: Create Directory Config, Merge Directory Configs, Create Server Config, Merge Server Configs
Request Phase Participation: Fixups
Module Directives:
    DAV - specify the DAV provider for a directory or location
    DAVMinTimeout - specify minimum allowed timeout
    DAVDepthInfinity - allow Depth infinity PROPFIND requests
Current Configuration:
    <Location /davtest>
      DAV on
    </Location>


Module Name: mod_dav_fs.c
Content handlers: none
Configuration Phase Participation: Create Server Config, Merge Server Configs
Request Phase Participation: none
Module Directives:
    DAVLockDB - specify a lock database
Current Configuration:
    DAVLockDB /tmp/DAVLock 


The <Location> container that I set up is simplified for testing purposes.  
The only indicator that something is wrong on the server side is that no
files get created in /tmp, despite the DAVLockDB directive.

I have LogLevel set to "debug", and it doesn't show any errors.  WebDAV was 
working fine before the upgrade to 2.0.55.  Does anyone have any ideas as 
to what might be going wrong?

Thanks,
Brent