[horde] SyncML suddenly failing

[Ole Wolf]

Quoting Jan Schneider <jan at horde.org>:
> Nothing suddenly stops working out of the blue. What did you do  
> before it started failing?

Indeed, and that's why I suspect the most recent upgrade to be the  
culprit. Backtracking, I can think of the following three changes on  
my server and Horde setup:

1. I added varnish as a http cache; however, this was on port 80 and  
syncing happened on port 443 (https), so caching port 80 shouldn't  
affect the sync. True enough, removing varnish again and thus  
restoring the web server setup didn't resolve the problem.

2. I had to deselect my default address book and reselect it again in  
order to be able to add public PGP keys in Horde. Not sure why this  
was necessary. However, when I sync only to, say, the calendar and not  
the address book, I get the same error message.

3. I upgraded Horde to the most recent version.

>   This should have only happened with an intermediate version of  
> Horde_Xml_Wbxml from Git.

I haven't installed Horde via Git, so could it be that the official  
release includes the intermediate version that are installed via PEAR?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 5253 bytes
Desc: PGP Public Key
URL: <http://lists.horde.org/archives/horde/attachments/20110924/f5775560/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4045 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/horde/attachments/20110924/f5775560/attachment-0001.bin>