A WebDAV server can be embedded in a context where not everything around it is WebDAV; for example, there could be some web site with a /files/ section that is WebDAV enabled and uses webdav-js as its index.html (or, more atypically, a single folder could have WebDAV disabled).
When directory navigation reaches such a point, a PROPFIND ${path} failed: Not Allowed (405) message is shown, and the view keeps spinning. The better behavior IMO would be to fall back to just navigating the browser there -- chances are it will succeed in a GET and can do something more sensible.
A WebDAV server can be embedded in a context where not everything around it is WebDAV; for example, there could be some web site with a
/files/section that is WebDAV enabled and uses webdav-js as its index.html (or, more atypically, a single folder could have WebDAV disabled).When directory navigation reaches such a point, a
PROPFIND ${path} failed: Not Allowed (405)message is shown, and the view keeps spinning. The better behavior IMO would be to fall back to just navigating the browser there -- chances are it will succeed in a GET and can do something more sensible.