Heads-up.. US Government websites to require HTTPS by end of 2016...

As this article says:

[quote]Following the lead of many major Web services, the White House on Monday announced that it would move all of the federal government

Hi
I should be able to do this OK
e.g for the NOAA forecast download
will the ftp download option change/still be available?

will there be a test site?

for the noaa warning program , I will have to re write that (I do have code from the Mac version of that)
This is more reason for people to have to upgrade from build 81 of WD…

My point forecast is available as https, but:

"There is a problem with this website

Just did a bit of testing with the key sites:

www.weather.gov uses an invalid security certificate.
The certificate is only valid for the following names:
*.akamaihd.net, *.akamaihd-staging.net, a248.e.akamai.net, *.akamaized.net, *.akamaized-staging.net
(Error code: ssl_error_bad_cert_domain)

forecast.weather.gov uses an invalid security certificate.
The certificate is only valid for the following names:
*.akamaihd.net, *.akamaihd-staging.net, a248.e.akamai.net, *.akamaized.net, *.akamaized-staging.net
(Error code: ssl_error_bad_cert_domain)

dualicons-forecast.weather.gov has not enabled HTTPS …
just times out.

earthquake.usgs.gov uses an invalid security certificate.
The certificate is only valid for the following names:
*.akamaihd.net, *.akamaihd-staging.net, a248.e.akamai.net, *.akamaized.net, *.akamaized-staging.net
(Error code: ssl_error_bad_cert_domain)

So they aren’t quite ready for testing… just have to wait for announcements.

It’s my understanding that the NWS is deprecating all FTP access to data in favor of HTTP (and now maybe HTTPS).

I found the site https://https.cio.gov/ to be quite helpful in explaining in more detail what is mandated and caveats for implementation on Federal websites.

Best regards,
Ken

https://www.whitehouse.gov/ is good :wink:

Yes, but very little useful weather data there :slight_smile:

You’d kinda expect the CIO to make sure the Executive website is compliant with the memoranda.

It's my understanding that the NWS is deprecating all FTP access to data in favor of HTTP (and now maybe HTTPS).
yeah, I suspected that so I better look to if that setting is in use to change it to HTTP instead, for now

Same for http://weather.noaa.gov/ where WD gets METAR data from.

Same for http://weather.noaa.gov/ where WD gets METAR data from.
the goal will be that this will need to change to Same for https://weather.noaa.gov/ and use SSL?

Not always a good assumption in my experience :lol:

Probably… it would likely be more convenient and easier to maintain long-term if you use a library function (something like curl ) so you just pass it the https:// URL and it returns the contents. That way you don’t have to worry about the underlying protocols (SSL, TLS, etc) which are subject to change and updates too.

Nor in mine… the wheels of government grind quite slowly except where ‘saving face’ is involved :slight_smile: