) are advertised as publishing a Last-Modified: header field, to allow efficient polling; but unfortunately, I can't see that this is the case. As an example with curl:
* Trying 54.77.164.226...
* TLS 1.0 connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA
* Server certificate: Symantec Class 3 Secure Server CA - G4
* Server certificate: VeriSign Class 3 Public Primary Certification Authority - G5
> GET /api/staticfeeds/4.0/serviceIndicators HTTP/1.1
> User-Agent: curl/7.43.0
> Accept: */*
> X-Auth-Token:my-token-goes-here
>
< HTTP/1.1 200 OK
< Date: Sat, 03 Jun 2017 11:07:59 GMT
< Server: Apache-Coyote/1.1
< Cache-Control: no-cache, no-store, max-age=0, must-revalidate
< Pragma: no-cache
< Expires: 0
< X-XSS-Protection: 1; mode=block
< X-Frame-Options: DENY
< X-Content-Type-Options: nosniff
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 9960
< Connection: close
<
{ [7668 bytes data]
* Closing connection 0
: cez@Ceri-no-Mac-mini;
I'm expecting to see a "Last-Modified:" header in the response, that I can use in concert with the "If-Modified-Since" request header to avoid re-fetching the data if it's not changed.