Issue metadata
Sign in to add a comment
|
fetch({cache: 'no-store'}) and fetch({cache: 'no-cache'}) stall other requests for the same resource |
||||||||||||||||||||||||
Issue descriptionChrome Version: 56.0.2924.76 OS: MacOS 10.12.2 If multiple fetch() calls request the same resource, we stall all requests but the first one to check caching headers and re-use the response if possible. If the fetch has mode: 'no-store' or mode: 'no-cache', that is not necessary, but we still do it. What steps will reproduce the problem? (1) Run the server in https://gist.github.com/surma/81ab7017a086bd55da9907f5ca10982c (2) Open DevTools Network panel (3) Navigate to http://localhost:8081 What is the expected result? All requests should start (and finish) at the same time. What happens instead? The requests are serialized.
,
Feb 3 2017
,
Feb 3 2017
Could this be due to resource scheduler? Requests by fetch have the lowest priority and before <body> only one request can go at a time.
,
Feb 3 2017
Yes most likely due to RS. We can check this by putting the <script> after <body>.
,
Feb 3 2017
Is this dup of issue 458620 ?
,
Feb 4 2017
,
Feb 4 2017
This might be due to issue 453190
,
Mar 15 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by csharrison@chromium.org
, Feb 3 2017