-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vdirsyncer 0.19: digest auth broken #1015
Comments
Just acknowledging that I saw this issue last week. This is indeed broken, I'll try to address it soon. |
Relevant: aio-libs/aiohttp#4939 |
Probably gonna have to copy chunks from aio-libs/aiohttp#2213 |
Pinning this issue since it's high priority to get this through. |
I have the same issue on a http remote:
results in:
|
A lot of the networking bits were re-written (in great part due to some dependencies being unmaintained themselves and not working on recent python versions). During this rewrite, I omitted Digest Auth. It needs to be implemented (and I'll get around to it as soon as I get a chance), but there's no workaround in the meantime. |
digest was a good keyword for me, it works when I change auth to basic (remote is a Zimbra server) 👍 |
It seems this bug prevents me from using |
Just want to say that Baikal does support basic authentication (at least v0.9.3). The method can be set in the admin web interface under system settings. It works with vdirsyncer for me. |
@clombt ah thanks, I haven't seen this. Thanks for the pointer! |
Hi @WhyNotHugo |
As there is no real progress on the underlying library, |
Yeah, I should have used Switching now would require rewriting a lot of the codebase, and I'm already focused on a whole rewrite. Adding digest auth to the new version will be easier. If someone wants to port the current version to |
For what it is worth, I am getting this trying to sync with Google. However, it is on some entries which I have not been able to track down. Otherwise, syncing works well. |
Depending on how far that rewrite is coming along, may I suggest implementing a temporary solution that makes vdirsyncer handle digest auth? It could use If there are no plans to do something like this, I would at least suggest reporting a friendlier error message instead of the error that is shown now. |
We're not using I agree that a better error message should be shown here. |
@duckunix Google does not use Digest Auth. Can you open a separate issue with your configuration and the whole error? It is likely a different issue. |
I meant that as in, use that method to generate the content of the |
When I updated from 0.18 to 0.19, 'vdirsyncer sync' broke.
with
-vdebug
:In case it matters, this is with Python 3.11.0 on NetBSD, aiohttp 3.8.3, server is running baikal 0.9.2
The config for the server looks like this:
Removing
auth
or setting it tobasic
doesn't work.The text was updated successfully, but these errors were encountered: