diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-24 01:21:35 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-24 01:21:35 +0000 |
| commit | 86de13da4552bd122f2787872f9c60394661f251 (patch) | |
| tree | 1d8c0985faff2c3505e6bf11b513047676a590b0 /base | |
| parent | 64144178c9070dd0e08abf0a70c5da87af0f1722 (diff) | |
| download | chromium_src-86de13da4552bd122f2787872f9c60394661f251.zip chromium_src-86de13da4552bd122f2787872f9c60394661f251.tar.gz chromium_src-86de13da4552bd122f2787872f9c60394661f251.tar.bz2 | |
ChromeFrame's host network stack implementation for IE full tab mode implicitly follows redirects.
When Chrome receives a notification about a redirect it also attempts to follow the redirect request. While
this works in most cases, some sites actually returned an error for the second request initiated by Chrome.
Fix is to abort the request in urlmon, when we receive a notification about a redirect. I also fixed the
IsRedirectResponse function in the UrlRequestAutomationJob class to only treat 301, 302, 303 and 307 as
redirect codes on the same lines as the default http job.
Test=covered by existing network tests.
I also verified that http://code.google.com/p/chromium/issues/detail?id=25643 works with this CL.
Fixes http://code.google.com/p/chromium/issues/detail?id=28296
Bug=28296
Review URL: http://codereview.chromium.org/402107
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@32896 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base')
0 files changed, 0 insertions, 0 deletions