Closed eiswurm closed 1 year ago
This happens because clients first send an unauthenticated request, and then log in using a second request. That is technically necessary in order to send the nonce
to the client, which it should use to encrypt the password. If your hoster blocks IP addresses so quickly, you should contact your hoster.
Baikal version: 0.9.2, WebDAV authentication type: Digest
My hoster blocks our current IP because of too many requests and 401. The following code can be found in the access_log of the Apache server. Is this rather an error of the client or of Baikal?
"PROPFIND /html/dav.php/calendars/somaye/ HTTP/1.1" 401 419 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/calendars/juergen/ HTTP/1.1" 401 420 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/calendars/firma/inbox/ HTTP/1.1" 401 424 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/calendars/somaye/ HTTP/1.1" 207 3642 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/calendars/juergen/ HTTP/1.1" 207 9974 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/calendars/firma/inbox/ HTTP/1.1" 207 387 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/addressbooks/somaye/ HTTP/1.1" 401 422 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/addressbooks/juergen/ HTTP/1.1" 401 423 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/calendars/firma/ HTTP/1.1" 401 418 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/addressbooks/juergen/ HTTP/1.1" 207 2092 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/addressbooks/somaye/ HTTP/1.1" 207 2094 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/calendars/firma/ HTTP/1.1" 207 6110 "-" "eMClient/9.2.1222.0" "REPORT /html/dav.php/calendars/somaye/default/ HTTP/1.1" 207 287 "-" "eMClient/9.2.1222.0" "REPORT /html/dav.php/calendars/juergen/emil/ HTTP/1.1" 207 288 "-" "eMClient/9.2.1222.0" "PROPFIND /html/dav.php/calendars/somaye/inbox/ HTTP/1.1" 401 425 "-" "eMClient/9.2.1222.0"