[horde] Sending HTTP 401 Unauthorized header response

[Michael J Rubinsky]

Quoting Arjen de Korte <build+horde at de-korte.org>:

> Possibly more log spam:
>
> 2019-01-04T13:23:44+01:00 ERR: horde Sending HTTP 401 Unauthorized  
> header response. [pid 1949 on line 126 of  
> "/usr/share/php7/PEAR/Horde/Rpc/ActiveSync.php"]
>
> Dumping $serverVars just a few lines before this line, it looks like  
> the client attempts to authenticate with type "Bearer" but there is  
> no token. I also see requests where the same client is using Basic  
> authentication with a base64 encoded username and password, which  
> works fine. The client in question is the built-in Windows 10 Mail  
> and synchronizes as usual.
>
> I've removed the account and recreated it, but the problem remains.

We don't support Bearer token authentication, so this is normal  
behavior. The server rejects the authentication and the client falls  
back to username/password. We can probably lower this to a DEBUG level  
though.

Thanks for the report, though.


> -- 
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 9272 bytes
Desc: PGP Public Key
URL: <https://lists.horde.org/archives/horde/attachments/20190104/f3f9f703/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 821 bytes
Desc: PGP Digital Signature
URL: <https://lists.horde.org/archives/horde/attachments/20190104/f3f9f703/attachment-0001.bin>