Joshua Slive wrote:
> What are you trying to accomplish? As I said, activating DAV without
> any DAV methods doesn't make any sense.
I was trying to see if I could give my users a public_html directory within
their DAV shares.
> In addition, the use of "Dav UserDir" implies you are using some
>
On 7/11/06, Brandon Fosdick <[EMAIL PROTECTED]> wrote:
Joshua Slive wrote:
> Show us the config and log entries. In general, activating DAV for a
> directory shouldn't change anything about GET/HEAD requests.
This is the relevant bit from httpd.conf
---
#Serve account public_html direct
Joshua Slive wrote:
> Show us the config and log entries. In general, activating DAV for a
> directory shouldn't change anything about GET/HEAD requests.
This is the relevant bit from httpd.conf
---
#Serve account public_html directories
DirectoryIndex index.html
On 7/11/06, Brandon Fosdick <[EMAIL PROTECTED]> wrote:
As a quick hack I tried enabling mod_dav on a location to see if it would act
as a storage backend for regular page serving. That is, just to use it for GET
and HEAD requests and none of the other DAV-related requests.
For the most part it
As a quick hack I tried enabling mod_dav on a location to see if it would act
as a storage backend for regular page serving. That is, just to use it for GET
and HEAD requests and none of the other DAV-related requests.
For the most part it works, but for some reason DirectorySlash and
Director
