Was just looking at this. FWIW the JSON version of the script is working for me if you want to try that temporarily.

Anyway, it's getting 301 redirected because the URL is http rather than https - at least that's what I'm seeing. I thought that was fixed in the code recently, but I'm looking at code based on version 4.02...

As required by US Department of Homeland Security BindingOperational Directive 18-01, NCEP/NCO will be making changes tothe underlying protocols that are used to access our public andinternal web sites. For web sites, the directive addressesenforcement of secure HTTPS protocols for all access.

These changes will include:

Enabling HTTPS for sites that were previously HTTP-only

Redirecting HTTP traffic for all sites to the respectiveHTTPS counterpart

Restricting HTTPS handshakes to Cipher suites that are knownto be secure.

Scripts that are attempting to connect to the HTTP servicethat do not honor the redirect to HTTPS will fail.

Scripts or applications that do not support HTTPS protocolswill be unable to connect.

Browsers that do not support secure ciphers may be unable toconnect (we believe that this would only affect browsers that arealready obsolete, but that does not mean that they are notpossibly still in-use. Example: IE8 on Windows XP)

Users who have restrictive firewall rules at their side thatdo not permit access to the HTTPS service may be unable toconnect.

Please be aware that all of the changes above are, in addition tobeing mandated by DHS, considered ā??best practiceā?? in networksecurity and privacy. For more information on the transition toHTTPS-only, please see https://https.cio.gov/