Well, this is..... interesting??
As of this morning, 4.03 is working. 5.05 is acting rather weird on NWS's side.
Here is the comment stream from the code:
<!-- File Name: https://forecast.weather.gov/MapClick.php?CityName=Lexington&state=MA&site=MTR&textField1=42.4399&textField2=-71.2405&e=1&TextType=2 -->
<!-- advforecast2.php (JSON) - V5.05 - 27-Feb-2018 on PHP 7.2.1-->
<!-- RAW NWS URL: https://forecast.weather.gov/MapClick.php?CityName=Lexington&state=MA&site=MTR&textField1=42.4399&textField2=-71.2405&e=1&TextType=2 -->
<!-- zone=MAZ014 -->
<!-- corrected NWS API URL='https://api.weather.gov/points/42.4399,-71.2405/forecast' -->
<!-- curl fetching 'https://api.weather.gov/points/42.4399,-71.2405/forecast' -->
<!-- note: fetched 'https://api.weather.gov/gridpoints/BOX/64,79/forecast' after redirect was followed. -->
<!-- HTTP stats: RC=404 dest=104.72.62.193 port=443 (from sce=74.208.114.109)
Times: dns=0.000 conn=0.031 pxfer=0.063 get=0.775 total=0.837 secs -->
<!-- headers returned:
HTTP/1.1 404 Not Found
Server: nginx/1.10.2
Content-Type: application/problem+json
Access-Control-Allow-Origin: *
Pragma: no-cache
X-Server-ID: vm-bldr-nids-apiapp22.ncep.noaa.gov
X-Correlation-ID: 99795aeb-e0cb-4d16-af5e-254f3f8ff3a8
X-Request-ID: 99795aeb-e0cb-4d16-af5e-254f3f8ff3a8
Cache-Control: private, must-revalidate, max-age=600
Expires: Thu, 01 Mar 2018 12:47:06 GMT
Date: Thu, 01 Mar 2018 12:37:06 GMT
Content-Length: 364
Connection: keep-alive
Vary: Accept
Strict-Transport-Security: max-age=15768000 ; includeSubDomains
-->
<!-- Oops.. point forecast unavailable RC=404 - using Zone instead -->
After this, the zone forecast loads fine. So... Why the 404? I tried loading the redirected URL in a browser and got this:
{
"correlationId": "2442b844-33f9-4e85-a3b4-f0b8316473c4",
"title": "Data Unavailable For Requested Point",
"type": "https://api.weather.gov/problems/InvalidPoint",
"status": 404,
"detail": "Unable to provide data for requested point 90,120.55176052112",
"instance": "https://api.weather.gov/requests/2442b844-33f9-4e85-a3b4-f0b8316473c4"
}
So the API thinks I'm trying to get the forecast for the North Pole? Hmmm.