0
Answered

There was an invalid response to an authenticated webdav request

puurlek 2 years ago updated by Vlad R 2 years ago 2
When trying to connect to my FileRun installation, running on HTTPS, with Nextcloud or ownCloud, I get the error stated in the title, after entering the correct login information. I have not made additional configurations to Nginx for Webdav compatibility. Is this necessary? A nudge in the right direction would be very appreciated.


Answer

Answer
Answered

A solution was found in the following NGINX guide: "https://www.nginx.com/resources/wiki/start/topics/examples/phpfcgi/".
The correct handling of PATH_INFO enabled FileRun's URL "http://hostname/dav.php/" (note trailing slash) to work properly and allow WebDAV access.

Under review

I don't think we've ever tested FileRun's WebDAV access when running directly on NGINX. There isn't much troubleshooting information either, but if you contact us via e-mail and provide us temporary access to your FileRun installation, we can check the HTTP communication between a Nextcloud client and your server, to see what goes wrong.

Answer
Answered

A solution was found in the following NGINX guide: "https://www.nginx.com/resources/wiki/start/topics/examples/phpfcgi/".
The correct handling of PATH_INFO enabled FileRun's URL "http://hostname/dav.php/" (note trailing slash) to work properly and allow WebDAV access.