Web Weather > Weather Web Site Help

check-fetch-times.php

(1/1)

yamiacaveman:
pennlake.us

Using the "check-fetch-times.php" I have one that always is not successful;

 Skipped cache write test to ./cache/forecast-PAZ047-test-json.txt file.
Test was NOT successful.
--end NWS Forecast URL check --

So just looking for what this means, and if a problem how to correct?

Thanks for any help,

yamiacaveman

saratogaWX:
Your site shows
--- Quote -----checking NWS Forecast URL --
Using first entry in Settings.php $SITE['NWSforecasts'] for test.
URL: https://api.weather.gov/points/41.1131,-75.7749/forecast
Cache: ./cache/forecast-PAZ047-test-json.txt
 curl fetching 'https://api.weather.gov/points/41.1131,-75.7749/forecast'
 HTTP stats:  RC=301 dest=23.222.21.139 port=443 (from sce=173.230.251.210)
      Times: dns=0.007 conn=0.215 pxfer=0.649 get=0.616 total=1.265 secs
RC=301 Moved Permanently, bytes=958
------------
Headers returned:

HTTP/1.1 301 Moved Permanently
Server: nginx/1.10.2
Content-Type: application/problem+json
Location: /gridpoints/BGM/76,12/forecast
Access-Control-Allow-Origin: *
Pragma: no-cache
X-Server-ID: vm-lnx-nids-apiapp23.ncep.noaa.gov
X-Correlation-ID: 5a7b12e4-ae11-45f9-89ce-f3e6d826d8b9
X-Request-ID: 5a7b12e4-ae11-45f9-89ce-f3e6d826d8b9
Content-Length: 348
Cache-Control: private, must-revalidate, max-age=600
Expires: Sat, 07 Apr 2018 14:56:04 GMT
Date: Sat, 07 Apr 2018 14:46:04 GMT
Connection: keep-alive
Vary: Accept
Strict-Transport-Security: max-age=31536000 ; includeSubDomains ; preloa
------------

Skipped cache write test to ./cache/forecast-PAZ047-test-json.txt file.
Test was NOT successful.
--end NWS Forecast URL check --
--- End quote ---

Using check-fetch-times.php?show=versions on your site shows
--- Quote ---check-fetch-times.php   Need update to
V1.23 - 2018-03-26   V1.23 - 2018-03-26   V1.19 - 2017-10-17   check-fetch-times.php Version 1.19 - 17-Oct-2017

--- End quote ---
Your downlevel version of check-fetch-times.php (V1.19) did not have the proper fix for checking access to the NWS main forecast URL by following the 301 redirect to the gridpoint forecast instead.

The updated version of the script does have that fix.

yamiacaveman:
Yep, that did it, thanks Ken!!

Navigation

[0] Message Index