94a1560d31
Currently we default to assuming the cache is up-to-date. This is likely wrong. Normal web servers provide Last Modified for files they serve. If it is absent, chances are high the image is served by some sort of a dynamic service, which may modify the URL on fly. In any case, always updating the image is a safer choice. Change-Id: I0548db14a97638d26ebb687e8f47f1b295d1f774
9 lines
364 B
YAML
9 lines
364 B
YAML
---
|
|
fixes:
|
|
- |
|
|
When an ``http(s)://`` image is used, the cached copy of the image will always
|
|
be updated if the HTTP server does not provide the last modification date
|
|
and time. Previously the cached image would be considered up-to-date, which
|
|
could cause invalid behavior if the image is generated on fly or was modified
|
|
while being served.
|