diff options
| author |  Scott Leggett <scott@sl.id.au>
| 2024-07-02 23:12:53 +0800 |
|---|---|---|
| committer |  Frédéric Guillot <f@miniflux.net>
| 2024-07-02 22:05:49 -0700 |
| commit | bf1c8510930155a6f0e07de35149b360e61af3a6 (patch) | |
| tree | 388e8988441586936ee6970e6f51713746f94e2a /internal/database/migrations.go | |
| parent | c787bb5b482c772a1e650f9c97d211ea228e5cde (diff) | |
| download | v2-bf1c8510930155a6f0e07de35149b360e61af3a6.tar.gz v2-bf1c8510930155a6f0e07de35149b360e61af3a6.tar.zst v2-bf1c8510930155a6f0e07de35149b360e61af3a6.zip | |
fetcher: use ETag as a stronger validator than Last-Modified
As per the MDN article on HTTP caching:
During cache revalidation, if both If-Modified-Since and If-None-Match
are present, then If-None-Match takes precedence for the validator.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching
Previously Miniflux would consider a resource unmodified if the
Last-Modified header had not changed, even if the ETag had changed.
With this commit, Miniflux will consider a resource modified if the ETag
header has changed, even if Last-Modified has not.
This fixes Bug 1 in https://rachelbythebay.com/w/2024/06/11/fsr/
Diffstat (limited to 'internal/database/migrations.go')
0 files changed, 0 insertions, 0 deletions