HTTPS failing for DataPoint Weather feeds

[Paul Simmonds]

I am trying to use the Datapoint weather XML information.

I have it working fine locally!

When I upload my working web page to my website it fails to work;  the root cause is that the data feed is not supporting HTTPS (only HTTP);

The problem with any client side application is that the client side web page is HTTPS by default, and any modern browser does not allow an HTTP feed into an HTTPS page. (for very good security reasons).

Clearly, as HTTPS is now the recommended default for any web site, the DataPoint data feed ** MUST ** also support HTTPS.

Is this a bug / oversight / or can anyone suggest a work around??

Thanks

Paul

[Starbeamrainbowlabs]

I'd suggest proxying requests through some server-side logic. Remember that if you're directly making requests on the client side that means clients have access to your API key as well - and can potentially abuse it too.

[Alistair McClymont]

This is an issue for me too. Is there no https option for the API. Most APIs seem to be designed for use client side. There's other ways of ensuring API at the met office side of things, but looks like they aren't doing that kind of thing!

[Wayne Stallwood]

This is due to messing up the certificates when directing this API through their CDN service (Akamai)  It's issuing Akamai certificates rather than one signed for datapoint.metoffice.gov.uk.  CDN configuration needs looking at.

This breaks CORS policies in most modern browsers.