For one thing, the URL of this form:


Is now redirecting to one using HTTPS:


Also, the redirect itself takes an excruciatingly long time.
So I just changed the URL to https directly...

The first time I tried any of the above using CURL this morning it worked, but then after that I started getting:

An error occurred while processing your request.

Reference #30.6f451160.1558531514.16ced4f6

It looks as if they've put some kind of Akamai proxy in the middle, which is fine for static content, but not so fine for a query of this nature.  Strange that it worked for me the very first time.  It's almost as if the Akamai "farm" has lost some "state" information and not all nodes have the same content, so if you get stuck going through a bad node you get a bogus response.

Attached is a transcript of a failed attempt.  I put SOMESTATION there only after the fact.  The actual query was for my actual station, which used to work.

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/D629ECBA-956A-48D1-97F6-662D8A4EE70E%40isylum.org.
For more options, visit https://groups.google.com/d/optout.
curl -L -v 
"http://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=SOMESTATION&month=5&day=22&year=2019&format=1";
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* 
  Trying 184.27.188.101...
* TCP_NODELAY set
* Connected to www.wunderground.com (184.27.188.101) port 80 (#0)
> GET 
> /weatherstation/WXDailyHistory.asp?ID=SOMESTATION&month=5&day=22&year=2019&format=1
>  HTTP/1.1
> Host: www.wunderground.com
> User-Agent: curl/7.52.1
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Server: AkamaiGHost
< Content-Length: 0
< Location: 
https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=SOMESTATION&month=5&day=22&year=2019&format=1
< Cache-Control: max-age=0
< Expires: Wed, 22 May 2019 13:29:03 GMT
< Date: Wed, 22 May 2019 13:29:03 GMT
< Connection: keep-alive
< Set-Cookie: speedpin=4G; expires=Wed, 22-May-2019 13:59:03 GMT; path=/; 
domain=.wunderground.com; secure
< Set-Cookie: 
ci=TWC-Connection-Speed=4G&TWC-Locale-Group=US&TWC-Device-Class=desktop&X-Origin-Hint=dna&TWC-Network-Type=wifi&TWC-GeoIP-Country=US&TWC-GeoIP-Lat=42.3055&TWC-GeoIP-Long=-83.1724&Akamai-Connection-Speed=1000+&TWC-Privacy=exempt;
 path=/; domain=.wunderground.com; secure
< Property-id: drupal-prod
< X-RequestSource: AkamaiProdProxy
< TWC-Privacy: exempt
< TWC-GeoIP-LatLong: 42.3055,-83.1724
< TWC-GeoIP-Country: US
< TWC-Device-Class: desktop
< TWC-Locale-Group: US
< TWC-Connection-Speed: 4G
< X-RequestSource: AkamaiDefaultDNA
< 
* Curl_http_done: called premature == 0

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* Connection #0 to host www.wunderground.com left intact
* Issue another request to this URL: 
'https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=SOMESTATION&month=5&day=22&year=2019&format=1'
*   Trying 184.27.188.101...
* TCP_NODELAY set
* Connected to www.wunderground.com (184.27.188.101) port 443 (#1)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [102 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [2527 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [148 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=Georgia; L=Atlanta; O=TWC Product and Technology, LLC; 
OU=Digital; CN=www.weather.com
*  start date: Sep 25 00:00:00 2018 GMT
*  expire date: Nov 24 12:00:00 2019 GMT
*  subjectAltName: host "www.wunderground.com" matched cert's 
"*.wunderground.com"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert ECC Secure Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0x1724ea8)
} [5 bytes data]
> GET 
> /weatherstation/WXDailyHistory.asp?ID=SOMESTATION&month=5&day=22&year=2019&format=1
>  HTTP/1.1
> Host: www.wunderground.com
> User-Agent: curl/7.52.1
> Accept: */*
> 
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
} [5 bytes data]

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0< 
HTTP/2 503 
< server: AkamaiGHost
< mime-version: 1.0
< content-type: text/html
< content-length: 176
< cache-control: max-age=0
< expires: Wed, 22 May 2019 13:29:04 GMT
< date: Wed, 22 May 2019 13:29:04 GMT
< set-cookie: speedpin=4G; expires=Wed, 22-May-2019 13:59:04 GMT; path=/; 
domain=.wunderground.com; secure
< set-cookie: 
ci=TWC-Connection-Speed=4G&TWC-Locale-Group=US&TWC-Device-Class=desktop&X-Origin-Hint=dna&TWC-Network-Type=wifi&TWC-GeoIP-Country=US&TWC-GeoIP-Lat=42.3055&TWC-GeoIP-Long=-83.1724&Akamai-Connection-Speed=1000+&TWC-Privacy=exempt;
 path=/; domain=.wunderground.com; secure
< property-id: drupal-prod
< x-requestsource: AkamaiProdProxy
< twc-privacy: exempt
< twc-geoip-latlong: 42.3055,-83.1724
< twc-geoip-country: US
< twc-device-class: desktop
< twc-locale-group: US
< twc-connection-speed: 4G
< x-requestsource: AkamaiDefaultDNA
< 
{ [176 bytes data]
* Curl_http_done: called premature == 0

100   176  100   176    0     0    108      0  0:00:01  0:00:01 --:--:--   261
* Connection #1 to host www.wunderground.com left intact
<HTML><HEAD><TITLE>Error</TITLE></HEAD><BODY>
An error occurred while processing your request.<p>
Reference&#32;&#35;30&#46;5c451160&#46;1558531744&#46;1e332837
</BODY></HTML>

Also, it doesn't appear to be an authentication issue.
I just used a web browser and logged in to WU as I would to manage my station, then went to the WXXDailyHistory URL and it still failed.

Mind you, I am still using the old old old style password, not any so-called api key.  :-/

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)

On May 21, 2019, at 11:53 PM, gjr80 <[email protected]> wrote:

Hmm, I notice that WXDailyHistory is working as usual now (well for me anyway) but wunderfixer still gives a 403 error.

Gary

On Wednesday, 22 May 2019 13:02:24 UTC+10, gjr80 wrote:
Wunderfixer (as it stands now) relies on WUs WXDailyHistory.asp page. If WXDailyHistory doesn't work then wunderfixer will not work. Period.

I guess depending on where you sit on the conspiracy theory scale will determine whether you believe the current issues with WXDailyHistory are short term glitches or a silent closure of the service. There are a few threads on wxforum.net that touch on this issue, and of course many others that touch on the WU issues over the last not so long period. There seems to have been a few posts from WU staff indicating that 'all the old stuff is very fragile', so that could mean short term glitch, but on the other hand WU has been pushing folks towards their 'new' API which could mean the end for WXDailyHistory.

The 'new' WU API that is available to PWS owners/uploaders does have a '1 day rapid history request' that provides what seems like the same sort of info as WXDailyHistory, albeit in JSON format and with a whole pile more cruft, well at least as far as wunderfixer is concerned. So in theory there is no reason wunderfixer could not be reworked to utilise the '1 day rapid history request' data. Of note to use the new API you need to have a (new) API key, whereas WXDailyHistory/wunderfixer does not require an API key. One shortcoming I did notice with the '1 day rapid history request' is there appears to be no way to obtain a given days data; you get the current day only, whereas with WXDailyHistory you can choose the date required, so that would mean no more historical wunderfixing.

In any case, those who may consider WU as a de facto backup may want to start brushing up on their bash/MySQL skills and implement a robust local backup arrangement (though on WUs form you should have done that ages ago).

Gary

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/fac9e205-aca1-4376-92d6-b1ddcb889d19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/D629ECBA-956A-48D1-97F6-662D8A4EE70E%40isylum.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to