-
Notifications
You must be signed in to change notification settings - Fork 293
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
401 errors #1204
Comments
Authentification for users Fail after update. I hope this problem has not been reported before and it is not just a stupid failure on my part, sorry this is possible. Using: I updated my server to php 8.2, after realizing failure with baikal 0.9.2, I updated to 0.9.3 and also implemented the fixes from #1154. Response status code does not indicate success: '401' ('Unauthorized'). Message: Same for 'Authorization: Basic', I tried with prio existing users and new users, no login. Also, after downgrading back to 0.9.2. no authorization. What do I miss? Prosa: |
I am also using Baikal 0.9.3 and PHP 8.2 |
This issue is closed for me, update to baikal 9.4 made it, thank you! |
This error still persists in Baikal v. 0.10.1 when accessed from the default Mac calendar app.
|
Hi everyone,
I am running current baikal server and getting these 401 errors alternating with 207:
"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 401 2673 "-" "macOS/13.1 (22C65) dataaccessd/1.0"
"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 207 2512 "-" "macOS/13.1 (22C65) dataaccessd/1.0"
"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 401 2673 "-" "macOS/13.1 (22C65) dataaccessd/1.0"
"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 207 2512 "-" "macOS/13.1 (22C65) dataaccessd/1.0"
"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 401 2673 "-" "macOS/13.1 (22C65) dataaccessd/1.0"
"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 207 2512 "-" "macOS/13.1 (22C65) dataaccessd/1.0"
This error pattern also occurs when using Android. Calendar sync is working on all devices.
my apache config:
The text was updated successfully, but these errors were encountered: