Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: "Loyal" <loyal@bellosogno.com>
To: <dev@httpd.apache.org>
Subject: some advice re: custom WebDav (mod_dav)
Date: Thu, 12 Mar 2009 18:50:48 -0700
Message-ID: <CB5758CFAE0943CDBB65E1AA402BDD25@klhome>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcmjfiE4q8zlAlY5Quu4stzgsSdztg==

Hi all,

I'm building a Web service that must accept small (1-50k) files pushed to it
via the WebDAV protocol. I would like the Web server's DAV service to
process the files immediately (stuffing the contents into a MySQL table). I
also want to prevent any users from reading any files present (return an
empty directory), while still allowing writing clients to read back what
they wrote for a short time, say, a few minutes from the same IP, so that
their DAV writes don't fail. I would like to check the filenames of the
incoming writes and reject any that don't match an active user's ID (my form
of auth). Otherwise, access to the drop directory would be completely open
(no auth). 

To accomplish all this, I thought I'd create a modified version of mod_dav
for Apache and run this non-standard config on a dedicated box. 

Anybody WebDAV experts out there with an opinion on my thinking here?  Am I
nuts to try this?