| Summary | Sync4j / horde rpc doesn't work over HTTPS |
| Queue | Horde Base |
| Queue Version | 3.1.1 |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | karsten (at) horde (dot) org |
| Requester | jochem (at) mondrian-it (dot) nl |
| Created | 5/11/06 (7352 days ago) |
| Due | |
| Updated | 5/12/06 (7351 days ago) |
| Assigned | 5/11/06 (7352 days ago) |
| Resolved | 5/12/06 (7351 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
State ⇒ Resolved
See:
http://lists.horde.org/archives/sync/Week-of-Mon-20060508/001004.html
State ⇒ Assigned
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Sync4j / horde rpc doesn't work over HTTPS
Queue ⇒ Horde Base
State ⇒ Unconfirmed
request of Karsten Fourmont [fourmont@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