Armadietto: If-None-Match Discrepancy

I’ve installed Armadietto, and under some unclear circumstances, clients will not see new records created by other clients. I’m looking at the HTTP requests, and I see the client sending an If-None-Match header with the value “1642646049201”, and the server replying 304 Not Modified, but with an ETag of “1642649550275”. That’s wrong, yes?

Accept: /
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9,de;q=0.8
Authorization: Bearer 2Ftxf4xuDpTcGu3fT6uL+LVt6RA=
Cache-Control: no-cache
Connection: keep-alive
DNT: 1
If-None-Match: “1642646049201”
Pragma: no-cache
sec-ch-ua: " Not A;Brand";v=“99”, “Chromium”;v=“98”, “Google Chrome”;v=“98”
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: “macOS”
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: cross-site
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.55 Safari/537.36

Response: 304 Not Modified
Access-Control-Expose-Headers: Content-Length, Content-Type, ETag
Cache-Control: no-cache
Connection: Keep-Alive
Date: Thu, 20 Jan 2022 03:35:29 GMT
ETag: “1642649550275”
Keep-Alive: timeout=5, max=99
Server: Apache/2.4.52 (Debian)
Strict-Transport-Security: max-age=31536000; preload

One difference between the installations where I see this issue, and where I don’t: where I see the issue, I’m using the version from npm, which appears to be from four years ago. Where I don’t see the issue, I’m using the master branch. There have been a lot of commits since then - maybe it’s time for a new release?


4 years? Indeed, time to npm publish.

It’s getting some traffic on npm.

I think we could try to get most of the currently open PRs merged before tagging a release. Would be nice to have e.g. the front-end update in there, so it looks a bit nicer and works properly on mobile screens.

Let’s talk about it in the call tomorrow?

1 Like