Mark, the OpenChargeMap API has just changed to force redirecting to the https version -- basically a good idea. That broke the Android App OCM implementation: the standard Android InputStream class conveniently opens streams from URLs, but does not follow redirects. I've changed all API URLs to https, should have done so before when https became available for OCM. Maybe the iOS reader is smarter here, but maybe you should check that. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Mark, Christopher (still with us?), the OCM API server is currently near overload, I assume due to the https migration. 3 of 5 API requests currently fail with status 500. I've checked the OCM forum for some info and found this related topic: https://community.openchargemap.org/t/notice-api-will-shortly-require-an-api... Mark, do we have an OVMS account at OCM? If so, can you get an API key for us? I'm preparing the next Andriod update. Maybe hosting an OCM mirror is also an option, but no idea about the capacity needed. An API server with https may need quite some ressources, as there are nearly no reusable SSL sessions. According to Google we've got 1051 active Android installations. I did implement caching and incremental updates long ago, every App will normally only do ~ one update call per day (if it succeeds…). Regards, Michael Am 27.11.19 um 21:30 schrieb Michael Balzer:
Mark,
the OpenChargeMap API has just changed to force redirecting to the https version -- basically a good idea.
That broke the Android App OCM implementation: the standard Android InputStream class conveniently opens streams from URLs, but does not follow redirects.
I've changed all API URLs to https, should have done so before when https became available for OCM.
Maybe the iOS reader is smarter here, but maybe you should check that.
Regards, Michael
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Yep, we can register the App and provide an API key. I will eMail it to your privately (although it will end up in the source code anyway, or could be sniffed off the wire without too much difficulty). Regards, Mark.
On 2 Dec 2019, at 2:12 AM, Michael Balzer <dexter@expeedo.de> wrote:
Mark, Christopher (still with us?),
the OCM API server is currently near overload, I assume due to the https migration. 3 of 5 API requests currently fail with status 500.
I've checked the OCM forum for some info and found this related topic:
https://community.openchargemap.org/t/notice-api-will-shortly-require-an-api...
Mark, do we have an OVMS account at OCM? If so, can you get an API key for us? I'm preparing the next Andriod update.
Maybe hosting an OCM mirror is also an option, but no idea about the capacity needed. An API server with https may need quite some ressources, as there are nearly no reusable SSL sessions. According to Google we've got 1051 active Android installations. I did implement caching and incremental updates long ago, every App will normally only do ~ one update call per day (if it succeeds…).
Regards, Michael
Am 27.11.19 um 21:30 schrieb Michael Balzer:
Mark,
the OpenChargeMap API has just changed to force redirecting to the https version -- basically a good idea.
That broke the Android App OCM implementation: the standard Android InputStream class conveniently opens streams from URLs, but does not follow redirects.
I've changed all API URLs to https, should have done so before when https became available for OCM.
Maybe the iOS reader is smarter here, but maybe you should check that.
Regards, Michael
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
participants (2)
-
Mark Webb-Johnson -
Michael Balzer