We've recently made that move to all-HTTPS, as our moodle site now sits behind a reverse proxy (Forefront TMG) which makes it more sensible to operate that way.
The mobile app works fine externally for us, using the https:// address (using a wildcard certificate our IT folks sorted out) - but is currently not playing ball internally on college wifi as we send everyone straight to the moodle server via DNS and not FFTMG. The internal certicate isn't signed by an external authority so the app panics.
We still need to try putting the external wildcard certificate onto moodle internally, in a quiet window.
But other than that it runs fine.
Thanks for your reply. I realise that I was too brief in my explanation, sorry,
Yes, the mobile app works with https, but only with a trusted certificate. I'm planning to use moodle in a smallscale environment, for tracking progress for a group of softball pitchers, so I created a self-signed certificate on my server. And that is not accepted by the mobile app.
I could of course get a real certificate, but I would like to try http first.
Unfortuantely it's real certificate signed by a proper authority or ignore the certificate, in the app's world.
Unless the app had a way of knowing how to verify its certificate, e.g. a setting that it got from the moodle site, but that would be extra work.
The issue I forsee is that we don't have the .key file for our wildcard certificate that is used externally, and whilst I have an agreement to try the switch at 5pm today I won't know til then.
