Has anyone managed to get webdav working with Orthanc when using registered users+SSL all behind a reverse proxy?
I realize this is likely a rare use case, so the chances there’s anyone out there in the same boat are slim, but it’s worth asking.
I am using a Docker setup with the Osimis Orthanc images. The SSL and Registered users functions are turned on (so, Orthanc authentication is required) and the whole thing is additionally run from behind an Apache reverse proxy.
That seems to work great for the web explorer and DICOM node side, but not so much for webdav.
I was able to get the webdav working with a Docker setup, but only if I dropped all the other features I mention above: no registered users, no SSL, and no reverse proxy. So I know that the feature works on my hardware.
In my full SSL/authentication/proxy setup, when I turn on verbose logging and I add print out statements to my IncomingFilter, I can see that Orthanc does indeed receive the requests for the webdav folder and does not reject them. However, attempting to mount the webdav ends with a 403 error on the apache side of things. I don’t see Orthanc rejecting the request (in fact, it seems to be fine with the request), but the apache ultimately reports a 403 in its log.
I have been exploring how I might provide end users with access to their data other than the web portal. Webdav provides an interface that is familiar to users: their file browser. However, I don’t want to have to turn off security features like authentication and SSL to accomplish that goal.
Anyway, on the off chance there’s someone out here who has accomplished this kind of setup, I’d appreciate any suggestions!
Thanks,
John.