I have a WebDAV server set up, with its root folder /SomeVolume/webdav/contents
and address 192.168.1.2:12345
. User and password are set and the server can be accessed from a browser.
I am directing a domain name to the same machine using nginx, like this:
server {
server_name my.domain.me;
location / {
proxy_pass http://192.168.1.2:12345;
}
# plus the usual Certbot SSL stuff
This was working perfectly well, with HTTPS authentication and everything. I am using a third-party application that uses that server and it was working OK too.
I wanted to make this a bit more tidy and only changed couple of things:
- WebDav server root to
/SomeVolume/webdav
(instead of/SomeVolume/webdav/contents
), restarted the server. proxy_pass http://192.168.1.2:12345
changed toproxy_pass http://192.168.1.2:12345/contents
. Restarted ngninx.
Nothing else was modified.
I can still login through the browser, but the third-party application has stopped working because it gets authentication errors (401). Although if I try to login locally with http://192.168.1.2:12345/contents/
it works just fine.
What am I not understanding here? Is it some caching problem with the third-party application or have I misunderstood how location & proxy_pass work?
Thanks.