Link preload always shows a warning for cross domain iframe originated requests
Reported by
teodorma...@gmail.com,
Apr 13 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Download the test.html attached to the report. 2. Open a new tab in latest stable Chrome 3. Open Network tab of DevTools, make sure "Disable cache" is not checked 4. Drag&drop test.html into the window to open the file What is the expected behavior? Console does not show a warning. What went wrong? Console shows a warning about the file that was preloaded, not being used. While in reality, as can be seen on the screenshot, the preload was indeed effective. I can see how the file was not loaded from memory cache in the iframe's context, but it was found in disk cache regardless. It is also possible that if the URL explicitly prevents caching, the iframe context would issue a second network request to fetch it again. However in this specific situation, the warning in console is misleading. Did this work before? No Chrome version: 65.0.3325.181 Channel: stable OS Version: 10.0 Flash Version: This is not a duplicate of #735386. That issue is no longer reproducible in the latest stable build.
,
Apr 17 2018
+yoav. It seems technically challenging to remove the warning in this case, but maybe Yoav has thought of this use-case.
,
Apr 18 2018
preload belongs to the frame. The test case preload a script which is used in a separate frame. The preloaded script is used via MemoryCache, not via the preload store. Hence the warning is correct, and that preload is not matched. |
|||
►
Sign in to add a comment |
|||
Comment 1 by krajshree@chromium.org
, Apr 13 2018