[sync] Sync4j / horde rpc doesn't work over HTTPS

[Karsten Fourmont]

Hi,

strange. I just gave it a try with my Windows Mobile 5 phone and the 
latest synthesis client: https works without problems.

 > xxx.xxx.xxx.xxx - - [12/May/2006:17:01:16 +0200] "POST /horde/rpc.php
 > HTTP/1.1" 200 -
This seems to indicate that no output is produced. Anything in the other 
apache logs? error_log? general messages? I sometimes had my php crash 
with https. But I'm no apache expert so I just don't know.

  Karsten

Jochem Meyers wrote:
> I've tried both the PRO and the STD (2.5.0.63) version of Synthesis on
> PocketPC 2003, and I see the same thing happening. When accessing over HTTP,
> it works fine. Entries show up in /tmp/horde.log
> When switching to HTTPS, it does the following three HTTP POST requests,
> after which the client says 'invalid data'. horde.log remains empty.
> 
> xxx.xxx.xxx.xxx - - [12/May/2006:17:01:16 +0200] "POST /horde/rpc.php
> HTTP/1.1" 200 -
> xxx.xxx.xxx.xxx - - [12/May/2006:17:01:16 +0200] "POST /horde/rpc.php
> HTTP/1.1" 200 -
> xxx.xxx.xxx.xxx - - [12/May/2006:17:01:16 +0200] "POST /horde/rpc.php
> HTTP/1.1" 200 -
> 
> -----Oorspronkelijk bericht-----
> Van: Nathan Sharp [mailto:horde at nps.parcellsharp.net] 
> Verzonden: donderdag 11 mei 2006 18:27
> Aan: Chris Dillon
> CC: sync at lists.horde.org
> Onderwerp: Re: [sync] Sync4j / horde rpc doesn't work over HTTPS
> 
> Chris Dillon wrote:
>> Quoting Karsten Fourmont <fourmont at gmx.de>:
>>
>>> please file a bug for this on http://bugs.horde.org/
>>> So it won't get lost another time. Thanks
>> I have encountered this problem as well, but it does not appear to be
>> a bug in Horde, rather in the Sync4j plugin.  If you were to make
>> Horde available via both http and https, you would notice that the
>> Sync4j plugin never tries to use https, it will only try http, even if
>> you give it an https URL.  A traffic sniffer should reveal the same.
>>
>>
> I have used the Horde sync code with HTTPS using the Synthesis client on
> a Palm with no problems.  It warns about the self-signed certificate but
> lets you keep going.
>