Hi Chris, Le 26/02/2016 01:38, Chris a écrit :
> sorry just stumbled over this: Thanks for providing additional information. > On Wed, 3 Feb 2016 15:29:54 -0400 David =?iso-8859-1?Q?Pr=E9vot?= > <taf...@debian.org> wrote: >> Thatâs why there are already the following rewrite in >> /etc/owncloud/htaccess (symlinked from /usr/share/owncloud/.htaccess): >> >> RewriteRule ^/owncloud/\.well-known/carddav /owncloud/remote.php/carddav/ >> [R=301,L] >> RewriteRule ^/owncloud/\.well-known/caldav /owncloud/remote.php/caldav/ >> [R=301,L] > > The .well-known/* URLs needs to be at the top level of the installation > like: > >> RewriteRule ^/\.well-known/carddav /owncloud/remote.php/carddav/ > [R=301,L] >> RewriteRule ^/\.well-known/caldav /owncloud/remote.php/caldav/ [R=301,L] > > Clients are not expecting the .well-known in a subdir. On the other hand, you can’t expect an .htaccess file from a subdir to be used at all for a request on the top level. Now that I think again about it, James, I assume you were referring to the /etc/apache2/conf-available/owncloud.conf file (and not some file under /etc/owncloud/ as I initially assumed). I wonder if it will go in the way of some other webdav implementation, I’ll look into it and will consider it for the next upload, thank you both. Regards David
signature.asc
Description: OpenPGP digital signature
