In our previous episode (Friday, 03-Jan-2014), LuKreme said: > This second dav will generate errors:
After further testing (using cadaver) I now get this: cadaver http://webdav.example.net/ Authentication required for Randy on server `webdav.example.net'; Username: randy Password: wrongpassword Authentication required for Randy on server `webdav.example.net'; Username: randy Password: rightpassword Could not access / (not WebDAV-enabled?): 405 Method Not Allowed Connection to `webdav.example.net' closed. dav:!> The only change since my last post (and I am not sure it is relevant) is I added "AllowOverride All" inside the Location block. Most of the examples I see online are for using domains in the pattern www.example.com and www.example.com/webdav for webdav access. but we've never done this and always used a separate subdomain with its own virtualhost for the webdav access. I just can't get it to work with apache 2.4. -- "If it's a hobby to us and a job to you, why are you doing such a shoddy job?" - Linus Torvalds to Microsoft --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
