Commit b6d9c75
Restore --unsafely-treat-insecure-origin-as-secure flag for Blazor WASM Lighthouse scenario (#2157)
* Restore --unsafely-treat-insecure-origin-as-secure flag for Blazor WASM Lighthouse scenario
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Also accept cached (fromCache) responses in WASM caching check
The WASM caching enforcement check previously only accepted HTTP 304
(Not Modified) as proof that a .wasm resource was cached. However,
browsers may serve cached resources with HTTP 200 from disk/memory
cache without making a network round-trip at all. Puppeteer exposes
this via response.fromCache(). Both cases indicate the resource was
properly cached after the first page load, so both should be accepted.
Without this fix, the 'Second page load' step fails with:
Unexpected uncached wasm resource '...System.Runtime.InteropServices.JavaScript.*.wasm'
even though the resource is served from the browser cache.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>1 parent 38eea61 commit b6d9c75
1 file changed
+9
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
27 | | - | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
28 | 34 | | |
29 | 35 | | |
30 | 36 | | |
| |||
126 | 132 | | |
127 | 133 | | |
128 | 134 | | |
129 | | - | |
| 135 | + | |
| 136 | + | |
130 | 137 | | |
131 | 138 | | |
132 | 139 | | |
| |||
0 commit comments