as part of testing mobile clients (but of general value), we have enabled secure communication (SSL) for apps.dhis2.org. E.g. the demo is now available on both:
We are testing a cheap godaddy certificate for the server, and would appreciate any feedback on clients not supporting this by default. Especially any problems with browsers on mobile phones, as they typically have a smaller list of trusted certificate providers.
So, everyone with any kind of feature phone and GPRS/wap enabled:
- With the phone browser go to https://apps.dhis2.org/demo/mobile/index.action
- send me a mail with info on the client/browser you tested and if it worked fine (and the error if any).
If the phone supports java, it would be even better to know if this works:
Nice. On Android it says "there are problems with the security
certificate for this site - the name of the site does not match the
name of the certificate". I click "continue" and after that everything
works fine.
Hmm, seems it might be a misconfiguration, I get the same warning and the wrong certificate.. Will have to check it.
A bit strange that it worked on opera mini and with the one mobile client app I've managed to test with.
Jo
···
Den 4. nov. 2011 kl. 16.06 skrev Jan Henrik Øverland:
Works in Android Opera Mini, no messages at all.
On Fri, Nov 4, 2011 at 15:57, Lars Helge Øverland <larshelge@gmail.com> wrote:
Nice. On Android it says "there are problems with the security
certificate for this site - the name of the site does not match the
name of the certificate". I click "continue" and after that everything
works fine.
I get the right certificate with all my computer browsers as well, so it looks like it mostly works ok. Strange that it only seems to affect the default android browser.. Let me know if you get problems on any other platforms.
Jo
···
Den 4. nov. 2011 kl. 16.14 skrev Jo Størset:
Hmm, seems it might be a misconfiguration, I get the same warning and the wrong certificate.. Will have to check it.
I get the right certificate with all my computer browsers as well, so it looks like it mostly works ok. Strange that it only seems to affect the default android browser.. Let me know if you get problems on any other platforms.
I have confirmed that the problem is with the android browser not sending the hostname in the ssl handshake with apache. So it is not related to the specific certificate or a general problem.
