What to do with chrome sending extra requests?
Google chrome sends multiple requests to fetch a page, and that's -apparently- not a bug, but a feature. And we as developers just have to deal with it.
As far as I could dig out in five minutes, chrome does that just to make the surfing faster, so if one connection gets lost, the second will take over.
I guess if the website is well developed, then it's functionality won't break by this, because multiple requests are just not new.
But I'm just not sure if I have accounted for all the situations this feature can produce.
Would there be any special situations? Any best practices to deal with them?
Update 1: Now I see why my bank's page throws an error when I open the page with chrome! It says: "Only one window of the browser should be open." That's their solution to security threats?!!
Your best bet is to follow standard web development best practises: don't change application state as a result of a GET call.
If you're worried I recommend updating your data layer unit tests for GET calls to be duplicated & ensure they return the same data.
(I'm not seeing this behaviour with Chrome 8.0.552.224, by the way, is very new?)
How to Fix a Google Chrome Sending Request, If there are multiple tabs, all of those pages get stuck, but after some time all the tabs start loading concurrently. There are a few things you can do to fix this The ready function sends a POST request to commence an ajax conversion. This all works fine in Opera, FireFox,IE9, however Chrome keeps sending back an extra GET request after the initial (and all subsequent) POST requests. This extra GET totally breaks the conversation (and causes the page to reset in my case)
I saw the subjected behavior while writing a server application and found that earlier answers are probably not true.
Chrome distributes a single request into multiple http ones to fetch resources in parallel. In this case, it is an image which it fetches as a separate http get.
I have attached screen shot of packet capture through wireshark.
It is for a simple get request to port 8080 for which the server returns a hello message.
Chrome sends the second get request for obtaining favorite icon which you see on top of every tab opened. It is NOT a second get to cater time out or any such thing.
It should be considered another element that differs across browsers. However, doing things in multiple http requests in parallel is kind of a standard thing in browsers as of 2018.
Here is a reference question that i found latter
Chrome sends two requests SO
What to do with chrome sending extra requests?, Google chrome sends multiple requests to fetch a page, and that's -apparently- not a bug, but a feature. And we as developers just have to deal with it. As far as I As your application runs, and additional requests are sent to the server, those requests are going to show up here as well. As long as you've got this panel open, you'll be able to see all the history of everything that was requested by your application and what the server sent in response to those requests.
It also can be caused by
link tags with empty
href attributes, at least in Chromium (v41). For example, each of the following line will generate an additional query on the page :
<link rel="shortcut icon" href="" /> <link rel="icon" type="image/x-icon" href="" /> <link rel="icon" type="image/png" href="" />
It seams that looking for empty attributes in the page is a good starting point, either
Chrome browser. Partial content request, When Chrome sends a request for a mp4/video file, "Range: Chrome aborts after the first send() which is good I guess, because it wouldn't make a video as fast as possible, but for some, the extra data Chrome uses is not You can right-click on a link and a new context menu will appear that simply lets you send links to other devices where you use Chrome. If you’re using Chrome on iOS you’ll need to have the app
My observation of this characteristic (bug/feature/whatever) occurs when I am typing in a URL and the Autocomplete lands on a match while still typing in the URL. Chrome takes that match and fetches the page, I assume for the caching benefits that would occur when loading the page yourself....
double requests from Chrome, Does anyone know why Chrome is sending duplicate requests and what I can do to avoid this? -- R. Mark Volkmann Object Computing, Inc. In comparison, when I use curl and request the same page, I receive only one request. Same one request if I refresh the page in Safari. Why would Chrome send two requests for the same page? Edit: I've looked into the request.headers and found one difference: the accept header. Here is the header for the first request.
This behavior can be caused by SRC='' or SRC='#' in IMG or (as in my case) IFRAME tag. Replacing '#' with 'about:blank" has fixed the problem.
Here http://forums.mozillazine.org/viewtopic.php?f=7&t=1816755 they say that SCRIPT tags can be the issue as well.
chrome.webRequest, For this reason, the API does not provide the final HTTP headers that are sent to Starting from Chrome 72, an extension will be able to intercept a request only if it request API use request IDs, and you can optionally specify filters and extra On your computer, open Chrome. At the top right, click More Settings. Under "Privacy and security," click Cookies and other site data. Turn Send a "Do not track" request with your browsing traffic
ModHeader, Modify HTTP request and response headers. To download to your desktop sign into Chrome and enable sync or send yourself a The most popular Chrome extension to modify headers ** What can ModHeader do?** On your computer, open Chrome. Go to the site from which you want to get notifications. Select 'View site information' . Next to Notifications, select Allow from the drop-down menu.
What Is Mixed Content? | Web Fundamentals, These subresources can be things like images, videos, extra HTML, CSS, The secure portion here comes from the encryption added to the requests sent and received by the browser. Chrome blocks the insecure script. Add up to five people to a single request so you don’t have to juggle multiple reminders or transactions. Split transactions straight away Tap on a recent purchase in the app and instantly request
Google Chrome Privacy Whitepaper, In order to do this, Chrome will send a request to google.com each When browsing in incognito or guest mode, these extra checks do not Get more done with the new Google Chrome. A more simple, secure, and faster web browser than ever, with Google’s smarts built-in. Download now.