CLOSED FIXED8959
[S60] location.assign can't display http error 404 
https://bugs.webkit.org/show_bug.cgi?id=8959
Summary [S60] location.assign can't display http error 404
Krishna
Reported 2006-05-17 12:30:23 PDT
If a browser receives a client error (4xx) message upon sending a HTTP request, the server typically includes a diagnostic message. According to the specification (RFC2068, section 10.4), "the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents SHOULD display any included entity to the user." For the error 404 neither Safari nor S60 Web Browser display the diagnostic webpage. They should display the diagnositc information. Steps to reproduce: 1. Open Safari or S60 Web Browser 2. Open the attached page 3. Click the link "Next" Expected results: A page with 404 diagnostics information is displayed Actual results: It remains in the same page Test source: <html> <head> <title>Assign error 1A</title> <script type="text/ecmascript"> function fMain(){ location.assign("foo.html"); } </script> </head> <body> <p> Click <a href="#" onClick="fMain()">Next </a> and verify that HTTP 404 error is displayed. </p> </body> </html>
Attachments
location.assign source (323 bytes, text/html)
2006-05-17 12:32 PDT, Krishna 		no flags
Details
Patch rebuilt in S60WebKit env (7.29 KB, patch)
2006-06-04 13:02 PDT, David Carson 		zalan: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Krishna
Comment 1 2006-05-17 12:32:59 PDT
Created attachment 8369 [details] location.assign source Load this page to reproduce the defect.
Alexey Proskuryakov
Comment 2 2006-05-17 13:07:18 PDT
I cannot reproduce this issue with ToT. I can reproduce it with shipping Safari, but then it's just location.assign that doesn't work (as seen in JavaScript console): "Value undefined (result of expression location.assign) is not object." *** This bug has been marked as a duplicate of 3808 ***
David Carson
Comment 3 2006-05-24 11:39:07 PDT
Added Keywork PlatformOnly as it has been fixed in Tot.
Bradley Morrison
Comment 4 2006-05-29 08:33:14 PDT
Added EasyFix keyword as patch in duplicate error seems to be applicable in S60 branch.
Krishna
Comment 5 2006-05-30 10:35:16 PDT
TSW Error ID: EWWG-6KZ882
Bradley Morrison
Comment 6 2006-05-30 13:44:23 PDT
Reopening as this still exists on the S60 branch.
Krishna
Comment 7 2006-06-01 11:58:00 PDT
This is not reproducible on the Safari Webkit as of 01Jun2006. This is reproducible only on the S60 webkit as of 01Jun2006.
David Carson
Comment 8 2006-06-03 20:50:34 PDT
Just need to apply the same patch as 3808 to correct this issue. The patch includes a test case too. *** This bug has been marked as a duplicate of 3808 ***
David Carson
Comment 9 2006-06-04 13:02:26 PDT
Created attachment 8699 [details] Patch rebuilt in S60WebKit env patch and test case taken from 3808. Generated new kjs_window.lut.h file and added as part of the patch. Created new changelog entry.
alan
Comment 10 2006-06-19 18:33:02 PDT
Comment on attachment 8699 [details] Patch rebuilt in S60WebKit env r=me
Darin Adler
Comment 11 2006-06-30 21:35:27 PDT
Adding S60 prefix to summary of platform-only bugs with reviewed patches, so we can see if there are non-S60 ones in the review queue.
Bradley Morrison
Comment 12 2006-07-26 09:29:09 PDT
Committed as r15637 (applied patch, rebuilt and tested on latest S60WebKit to ensure patch still looks good). Many thanks!
Krishna
Comment 13 2006-07-27 08:47:49 PDT
As this is S60 only error, verified on the S60 Webkit at r15648. Clicking the link "Next" displays 404 error. Resolution is set to VERIFIED.
Krishna
Comment 14 2006-07-28 10:59:34 PDT
Set to CLOSED.
Joel Parks
Comment 15 2011-03-21 11:52:08 PDT
re-purposing InTSW keyword for use by QtWebkit team
Note You need to log in before you can comment on or make changes to this bug.