Follow PROPFIND redirects

Thank you for creating this library, I'm using it extensively and it works well for me.

I was wondering, if we can document the fact that certain Caldav servers return users to a different path on first PROPFIND.

For example, with the GMX provider (not sure which server implementation), I'm redirected to a sub-path (/begenda/dav/users) when doing a PROPFIND on the URI that is documented by the provider:

$ curl -XPROPFIND -vL https://caldav.gmx.net
...

< HTTP/2 302
< content-type: text/html
< date: Sat, 20 Sep 2025 20:10:46 GMT
< location: https://caldav.gmx.net/begenda/dav/users/

The login is only successful, when configured with that particular URI (not https://caldav.gmx.net):

• https://caldav.gmx.net/begenda/dav/users

Can we:

1. Document the behavior?
2. Implement an additional PROPFIND (to check the 302) before the first auth?

(1) is probably straight forward.

(2) will probably depend on the exact implementation in davclient.py the the standards..

[tobixen]

If you can write a pull request so that the 302 is followed, I will include it. Otherwise, I'll fix it myself when I get time. I don't think I will have time this year :-)

[tobixen]

@ghost - recently I've been getting authorization errors all the time with GMX. Is it only me, or do you have similar issues?

[tobixen]

Claude thinks that this issue will take 4-8 hours to fix, I think probably more like 2-3 hours. I do see complications writing good unit tests for it, but otherwise it should be fairly straight forward. At least if the redirects from GMX can be reproduced. It's a bit hard when GMX only delivers authorization errors. So that has to be resolved first.