Relanding this as this broke chrome frame net tests as we were not sending the response for the initial request initiated by IE. We need to check whether the request id on the initial request is -1 before deciding whether we should send over a response to Chrome.
Relanding this as this broke chrome frame net tests as we were not sending the response for the initial
request initiated by IE. We need to check whether the request id on the initial request is -1
before deciding whether we should send over a response to Chrome.

ChromeFrame would fail to load the page correctly if a manifest was specified in the html tag.
This would work the first time and fail on subsequent attempts. Basically the manifest specifies
portions of the website that is cached locally. In this case when there is a subsequent navigation
to the original URL the cached resource can be served out of the appcache which lives in chrome.

ChromeFrame expects the first url request from chrome to match that of the url which the user
navigated to. This url is served out of chrome'a app cache thus causing the pending url reques
checks to fail.

Fix is to validate the pending url request with the request received and stop the pending request
if there is no match. We just trace the fact and stop this request. A new request object is 
created to handle the request received and life goes on.

Fixes bug http://code.google.com/p/chromium/issues/detail?id=76439

BUG=76439
TEST=manually as described in the bug.
TBR=amit
Review URL: http://codereview.chromium.org/6736022

git-svn-id: http://src.chromium.org/svn/trunk/src@79369 4ff67af0-8c30-449e-8e8b-ad334ec8d88c

Former-commit-id: 2f94a3d9fd36c147d87ba3a8194507a6e3e1f2f1
meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser,meego-tablet-ux/meego-app-browser