[horde] ActiveSync stops working after migration from mod_php to mod_proxy_fcgi and PHP-FPM

[Arjen de Korte]

Citeren lst_hoe02 at kwsoft.de:

> Zitat von Arjen de Korte <arjen+horde at de-korte.org>:
>
>> I have migrated a (Apache 2.4) server from mod_php to  
>> mod_proxy_fcgi and PHP-FPM. This almost works, the only thing is  
>> that ActiveSync seems to have stopped working. In the webserver  
>> logs I see lots of lines like
>>
>>    192.168.1.133 - - [11/Jan/2014:12:39:33 +0100] "POST  
>> /Microsoft-Server-ActiveSync?Cmd=Sync&User=arjen&DeviceId=847CC7DCA0F0B1CF&DeviceType=Android HTTP/1.1" 401  
>> -
>>
>> After enabling ActiveSync debug logging at the same time the  
>> following is logged
>>
>>    2014-01-11T12:39:33+01:00 INFO: [12589]  
>> Horde_Core_ActiveSync_Driver::authenticate() attempt for arjen
>>    2014-01-11T12:39:33+01:00 NOTICE: Device failed to pass the user  
>> password.
>>
>> The same installation is operational again if I disable  
>> mod_proxy_fcgi and enable mod_php5, without further changes. What  
>> am I missing here?
>
>
> Maybe this one (taken from http://wiki.horde.org/ActiveSync ):
>
> You will need to configure your webserver to redirect the URL  
> /Microsoft-Server-ActiveSync to your horde/rpc.php file. How you do  
> this depends on your webserver and it's configuration. For Apache,  
> something like:
> 1
>
> Alias /Microsoft-Server-ActiveSync /var/www/horde/rpc.php
>
> Note: It has been reported that when running PHP via mod_fcgid on  
> Apache that the Alias directive will not pass the correct URL to the  
> fcgid-script handler. This can be worked around by using a  
> RewriteRule instead (adapted from  
> http://maurus.net/weblog/2010/10/26/running-z-push-1-4-2-with-apache-and-fastcgifcgid/):
> 1
> 2
>
> RewriteEngine On
> RewriteRule ^/Microsoft-Server-ActiveSync /horde/rpc.php [PT,L,QSA]

That's not the issue. The HTTP error returned is 401 (Unauthorized).  
You won't get that if the redirection to the horde/rpc.php file  
doesn't work, you'd get an 404 (Not Found) then. Since if I switch  
back to mod_php it works again, it must be an authorization issue.

Regards, Arjen