WXforum.net
Weather Related Organizations => NOAA National Weather Service => Topic started by: tmabell on March 08, 2018, 04:47:55 PM
-
With the ssl security issue at hand and the recent un-announced changes from http to https on many NWS web pages, I wonder if anyone has heard anything about when the WPC (Weather Prediction Center) and SPC (Storm Prediction Center) might be doing the government mandated change to https? As I read the mandate, all government sites should have done that already. Why those two are immune is a mystery to me. If they intend on doing it I wish they would just get it done so we can change what we need to change and move on.
-
We should add the CPC to the list of NOAA branches that seem to have a pass. ](*,)
-
We should add the CPC to the list of NOAA branches that seem to have a pass. ](*,)
CPC is not https:// compliant. I emptied the cache of both Chrome and Firefox (the latest version of each) on my machine to check. One refused to connect with https://, the other just timed out.
-
That is exactly the point I was going for.
-
And.. some of the sites use a Symantec-based cert which will be untrusted by Chrome and Firefox in the near future. I'm hoping the existing sites will replace any to-be-untrusted certs before the time runs out.
-
I just noticed today that the SPC has added ssl security. All of their products are available via https.
-
^^ That's too bad. Definitely not in the best interests of serving the public at large.
-
I just noticed today that the SPC has added ssl security. All of their products are available via https.
True enough, however a quick review of my SPC pages shows that SSL isn't strictly enforced as of now because the links to 'http://' are still valid and served. This gives us an opportunity to revise any scripts that use the SPC's images and data and obtain the 'padlock' on the address bar of those pages.
-
If anyone is using my SPC-based scripts, updated secure versions are now on my web site (https://www.gwwilkins.org/gwwScripts.php). They sort to the top by default.
Otherwise it's a matter of simply searching for 'http://' and replacing it with 'https://' in any script that uses SPC data/images.
-
FYI Curly's wxSPCreports.php (https://www.gwwilkins.org/wxSPCreports.php) is broken until the urls in 'inc-SPCreports.php' are changed from 'http://' to 'https://'.
-
Jerry,
Thanks for the info and updates!
-
I noticed this posted at the top of WPC's web site:
Please note: On July 10, 2018, WPC's web site will switch from the "http" protocol to the more secure "https" protocol. Please consider changing any bookmarked pages at that time. We will provide an update if there is a delay in this transition.
-
Indeed the WPC has transitioned to SSL. If anyone is using one of my WPC-based scripts, they have been updated to be SSL compliant and therefore now get the 'padlock' on the address bar. The
eight nine scripts updated 2018/07/17 (https://www.gwwilkins.org/gwwScripts.php) are now SSL compliant, plus a new WPC 3 Day Experimental FC Map script.
-
For those following this transition process here is the newest update: https://www.weather.gov/media/notification/pdfs/scn18-100ncep_urls.pdf (https://www.weather.gov/media/notification/pdfs/scn18-100ncep_urls.pdf)
-
I have not been able to access many of the NWS pages as of 12/17/2018, especially the local climate reports. What is very strange though, is that I have several computers on my home network. Out of the five I have tried, one computer can access those local climate pages but to the other four those are dead links. I have tried substituting "https" for "http" in my links but to no avail.
For instance: I can access "https://www.wrh.noaa.gov/sgx/obs/obs.php?wfo=sgx", which is the main Orange County, CA page but the internal link from that page, "https://w2.weather.govclimate/index.php?wfo=sgx", which is the local climate link, does not work.
-
I have not been able to access many of the NWS pages as of 12/17/2018, especially the local climate reports. What is very strange though, is that I have several computers on my home network. Out of the five I have tried, one computer can access those local climate pages but to the other four those are dead links. I have tried substituting "https" for "http" in my links but to no avail.
For instance: I can access "https://www.wrh.noaa.gov/sgx/obs/obs.php?wfo=sgx", which is the main Orange County, CA page but the internal link from that page, "https://w2.weather.govclimate/index.php?wfo=sgx", which is the local climate link, does not work.
That's an error and I thought is was something I did at my end somehow. But now I see you quoting it, so it must be something at their end.
There is no domain 'govclimate'. Add a slash between gov and climate like so: 'gov/climate'.
-
Adding the "/" between "gov" and "climate" did the trick. Corrected URL is "https://w2.weather.gov/climate/index.php?wfo=sgx". The internal links seem to be working now as well. Thanks for the tip!
I'm still wondering why the old links are working on two of my computers on my network but not all of the others. i also had a similar situation on my work computers (that are not in any way connected to my personal network). Strange!