Different tab network request will blocked in queen when request same url
Reported by
yaozeyua...@gmail.com,
Sep 14
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36 Example URL: http://chrome-bug-demo.bookflaneur.cn Steps to reproduce the problem: 1. get a url while block response for 10s(e.g chrome-bug-demo.bookflaneur.cn) 2. open 5 tab, and open the url in same time 3. the lase tab will be load after 5 * 10 => 50s, not 10s What is the expected behavior? different tab should not block same url request each other What went wrong? maybe network request map into request queen by url globally, so that same url in different tab mapped into same queen and been blocked, so if we append some suffix at url like ?v=1 / ?v=2, they will not be blocked Did this work before? N/A Chrome version: 69.0.3497.92 Channel: stable OS Version: 10.0 Flash Version:
,
Sep 14
I thought this had been resolved in Issue 472740 , and all the parallel requests in other tabs would read out of the cache entry written by the first network transaction. @morlovich, do you know how this is supposed to work?
,
Sep 14
It's not a complete solution --- in particular we can't share a parallel request if the first request is still waiting for headers, and that's what happens here (and things are max-age=0 to boot...)
,
Sep 14
Thanks for the info morlovich! In that case, probably the best solutions for this user are to either make the response cacheable, or speed up the server response. |
|||
►
Sign in to add a comment |
|||
Comment 1 by susan.boorgula@chromium.org
, Sep 14