Bug 74000

Summary: [Qt] HTTP redirect fails when irrelevant but incorrect encoding is specified
Product: WebKit Reporter: Allan Sandfeld Jensen <allan.jensen>
Component: WebKit QtAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: darin, hausmann
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Allan Sandfeld Jensen
Reported 2011-12-07 07:36:59 PST
Originally reported as NB#261819: PRECONDITIONS: Yandex set as a default search engine. STEPS LEADING TO PROBLEM: 1. Open Browser 2. Type e.g. 'car' into URL field and perform search 3. Perform another search (e.g. 'bad cars') 4. Repeat step 3. several times EXPECTED OUTCOME: Search i always performed properly. ACTUAL OUTCOME: At some point dialog pops up: "Cannot open page; Found" PRECONDITIONS: Yandex set as a default search engine. STEPS LEADING TO PROBLEM: 1. Open Browser 2. Type e.g. 'car' into URL field and perform search 3. Perform another search (e.g. 'bad cars') 4. Repeat step 3. several times EXPECTED OUTCOME: Search i always performed properly. ACTUAL OUTCOME: At some point dialog pops up: "Cannot open page; Found"
Attachments
Patch (2.11 KB, patch)
2011-12-07 07:48 PST, Allan Sandfeld Jensen 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Allan Sandfeld Jensen
Comment 1 2011-12-07 07:48:00 PST
Created attachment 118211 [details] Patch
Alexey Proskuryakov
Comment 2 2011-12-07 10:10:38 PST
Comment on attachment 118211 [details] Patch Please add a regression test.
Simon Hausmann
Comment 3 2011-12-07 11:12:06 PST
I agree with AP. It would be great if you could add a test or maybe you can find that there exists a test already that we are skipping and that can be unskipped with your patch. I suspect it would be somewhere in LayoutTests/http. Adding test coverage would be a great way to complete Kimmo's original work.
Allan Sandfeld Jensen
Comment 4 2011-12-08 03:43:06 PST
Additional testing reveals the issue has been resolved on a different level in trunk. This patch in platform is no longer necessary
Note You need to log in before you can comment on or make changes to this bug.