[Tickets #3920] NEW: Sync4j / horde rpc doesn't work over HTTPS

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=3920
-----------------------------------------------------------------------
 Ticket             | 3920
 Created By         | jochem at mondrian-it.nl
 Summary            | Sync4j / horde rpc doesn't work over HTTPS
 Queue              | Horde Base
 Version            | 3.1.1
 State              | Unconfirmed
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


jochem at mondrian-it.nl (2006-05-11 08:09) wrote:

Already posted to sync at lists.horde.org. I'm posting this as a bug by request
of Karsten Fourmont [fourmont at gmx.de].

When trying to synchronise (against a horde backend) using
https://domain.tld/horde/rpc.php, Sync4j attempts to sync for a very long
time, before throwing an error. When going to
https://domain.tld/horde/rpc.php in a browser, it works fine, and gives a
valid xml document:

<disco:discovery>
 <scl:contractRef ref="https://domain.tld/horde/rpc.php?wsdl"/>
</disco:discovery>

I switched apache from https to http, to see if https was the problem.
Synchronisation works fine over http.

I've also imported apache's certificate (IE doesn't complain about the
untrusted certificate anymore, so it's imported correctly), but to no
avail.

The device I'm using is an HP iPaq 6500, with PocketPC 2003