[sync] Funambol 6.0.13 sync failed with Horde SyncML module

[Jan Schneider]

Zitat von Karsten Fourmont <fourmont at gmx.de>:

> Hi,
>
> I tried the funambol outlook connector 6.0.9 beta with Horde.
>
> It seems the trouble comes from the gzip compression: The connector  
> asks for it and so Horde delivers it. But the connector seems to  
> choke on the compressed data.
>
> The funambol logs produce something like:
>
> 14:51:45 GMT +1:00 [DEBUG] - Reading response...
> 14:51:45 GMT +1:00 [DEBUG] - Content-length: 533
> 14:51:45 GMT +1:00 [DEBUG] - Receiving data of size 533...
> 14:51:45 GMT +1:00 [DEBUG] - Finished receiving data of size 533.
> 14:51:45 GMT +1:00 [DEBUG] - Response read:
> xœ¤T[oÚ0þ+(¯qÌ­´r\uclLÐMúî&²&q»úëçk".Y+•|rÎw.ßç“  
> ûCžuö´â)+Bú￾סEÌ’´Ø†Þz5펽{Œ¢c/æ
‰-xèqù”gwæ€>ôàgRaôD«Éj‚¥
k+ߟŠ  
> †Mà‚Ɖ"ÊU÷™Ì‚7ãÁpxh¼hÁ·*ˆ€1ЊT[*0š³x½œá
> ˺Ñ÷§_«—õˆô¦Ç¸¿Ìž·aˆ€(à#É)”5µŽh®XÄ^«˜ÖEwB”w
>
> As a workaround you can turn of the gzip compression in the horde setup:
>
> $conf['compress_pages'] = false; (in horde/conf.php)
>
> This seems to be a bug in the Funambol connector.
>
> But I found a glitch in Horde as well: I tried to create a "Browser  
> Quirk" so that
> if $browser->hasQuirk('buggy_compression') returns true in Horde.php.
> But the function Horde::allowOutputCompression() seems to be never  
> invoked! Do we need to invoke it in Horde::compressOutput()?

No, compressOutput() already checks for the quirk.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/