Hi Julien, On Mon, Jan 21, 2019 at 04:42:54PM +0100, Julien Cristau wrote: > +debian-admin > > On Mon, Jan 21, 2019 at 02:26:16PM +0100, Julien Cristau wrote: > > On Mon, Jan 21, 2019 at 09:27:19AM +0100, Philipp Hahn wrote: > > > Package: security-tracker > > > Severity: important > > > > > > Dear Maintainer, > > > > > > the JSON stream of the Debian Security Bug Tracker seems to report stale > > > data since the beginning of January 2019: > > > > > > $ curl -I https://security-tracker.debian.org/tracker/data/json > > > HTTP/2 200 > > > date: Mon, 21 Jan 2019 08:10:06 GMT > > > ... > > > content-length: 19836218 > > > last-modified: Wed, 02 Jan 2019 19:49:17 GMT > > > expires: Wed, 02 Jan 2019 20:57:34 GMT > > > > > > This breaks our process to monitor the Debian Security updates by > > > processing the DSAs in a machine-readable format. > > > > > Looks like at least one CDN node was returning stale data. I purged > > /tracker/data/json and things are looking ok now. Thanks for the > > report. > > > For the record, in case this comes back: I wasn't able to reproduce, but > both Philipp and Ansgar were getting stale data with a "x-cache: > UPDATING" header, from 23.111.9.35. For me from the same ip the data > was recent and "x-cache: HIT".
Looks this is happening again (or similarly): curl -I https://security-tracker.debian.org/tracker/data/json HTTP/2 200 date: Sun, 10 Feb 2019 16:23:01 GMT [...] last-modified: Wed, 06 Feb 2019 10:18:16 GMT cache-control: max-age=3600 expires: Wed, 06 Feb 2019 15:19:13 GMT x-clacks-overhead: GNU Terry Pratchett server: NetDNA-cache/2.2 x-cache: UPDATING Regards, Salvatore
