title: What to do with chrome sending extra requests?
body: <p>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.</p>
  
  <p>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.</p>
  
  <p>I guess if the website is well developed, then it's functionality won't break by this, because multiple requests are just not new.</p>
  
  <p>But I'm just not sure if I have accounted for all the situations this feature can produce.</p>
  
  <p>Would there be any special situations? Any best practices to deal with them?</p>
  
  <p>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?!!</p>