Network inspector keeps re-requesting 204 images when filtering
Reported by
papaspir...@gmail.com,
Jan 17 2017
|
|||
Issue descriptionChrome Version : 55.0.2883.95 && 57 When a page has a tracking pixel that is served with a 204 (No-content) header, Chrome will keep requesting it every time you filter the items in the Network tab. If I start typing "mypixel" in the filter box, Chrome will send out a request on each keypress (7 additional requests for the example given). *The additional requests do not appear in the network tab. I'm not sure if this is being included in Issue #614709 https://bugs.chromium.org/p/chromium/issues/detail?id=614709 This only happens for requests with 204 headers. Images served with 200 are only requested once. It also does not happen if the response has some caching headers. The issue can cause problems for analytics services that use 204 tracking pixels, such as Google Ads. Steps to reproduce: 1) Run a local server that serves 204 requests and log them. https://gist.github.com/lvrach/7dc58d576c3b33eae18c962784879240 2) Visit any page, add an image with src of the local server ( <img src="http://127.0.0.1:8333" /> ) 3) Open the network and start typing "127.0.0.1" in the filter box 4) Check the logs of the server for the number of requests received
,
Jan 17 2017
,
Mar 1 2017
For what it is worth, I believe that this issue is caused by the fact that the Network tab tries to render a small image thumbnail next to each request. For some reason this logic is flawed for 204 responses, and every time a 204 response is "touched" by the Network tab the request is invisibly repeated in an effort to render a thumbnail. (If you look closer you will actually see that the "broken image" icon next to the 204 response flashes briefly whenever the issue occurs.) The issue can also be reproduced by using a debugging proxy such as Charles. Reproducing the issue like this shows that the issue is also triggered by other things than just filtering - it is, for example, enough just to scroll up and down in the network tab past the 204 responses to make Chrome emit the extra requests.
,
Dec 1 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by shivanisha@chromium.org
, Jan 17 2017