[Webkit-unassigned] [Bug 243312] New: Safari does not respect Cache-Control: no-store, no-transform header when loading images

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=243312

            Bug ID: 243312
           Summary: Safari does not respect Cache-Control: no-store,
                    no-transform header when loading images
           Product: WebKit
           Version: Safari 15
          Hardware: Mac (Apple Silicon)
                OS: macOS 12
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: DOM
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: boris.brudnoy at healthometry.com

I create <img href="/data/sharing/qrcode"> elements dynamically in a web app and I have an HTTP service that receives GET requests like this:

GET /data/sharing/qrcode HTTP/1.1
Accept: image/webp,image/png,image/svg+xml,image/*;q=0.8,video/*;q=0.8,*/*;q=0.5
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.5 Safari/605.1.15
Accept-Language: en-CA,en-US;q=0.9,en;q=0.8
Connection: keep-alive

and responds like this:

HTTP/1.1 200 OK
Content-Type: image/png
Date: Thu, 28 Jul 2022 20:08:54 GMT
Content-Length: 425
Expires: Thu, 28 Jul 2022 20:08:54 GMT
Cache-Control: no-store, no-transform

Despite the presence of Cache-Control: no-store, no-transform, subsequent dynamically created <img> elements don't trigger new network requests, instead evidently using a cached image. When running the same web app in Chrome (Version 103.0.5060.134) I'm observing the behavior that seems expected to me, i.e. each time an <img> element like the above is created, a new HTTP request is issued.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220728/bf6eef68/attachment.htm>