Bug 18701

Summary: Clicking on redirect link stores wrong entry in history
Product: WebKit Reporter: Julien Lecomte <julien.lecomte>
Component: HistoryAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: ap, grahamperrin, mrowe
Priority: P2 Keywords: InRadar
Version: 525.x (Safari 3.1)   
Hardware: PC   
OS: Windows XP   
Attachments:
Description Flags
Test case none

Julien Lecomte
Reported 2008-04-23 13:24:06 PDT
If you click on a link that redirects you to another web site, and then look at your history, the redirect URL will have been stored. Instead, the final URL should have been stored. Safari is the only browser acting this way (Firefox, IE and Opera all store the final URL)
Attachments
Test case (261 bytes, text/html)
2008-04-23 13:27 PDT, Julien Lecomte 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Julien Lecomte
Comment 1 2008-04-23 13:27:06 PDT
Created attachment 20775 [details] Test case
Mark Rowe (bdash)
Comment 2 2008-04-23 13:36:25 PDT
I think the behaviour should be slightly different than you describe: a 301 (Moved Permanently) redirect should result in the destination URL being stored in history, while the temporary redirects (302, 303, 307) should result in the original URL being stored.
Mark Rowe (bdash)
Comment 3 2008-04-23 13:36:46 PDT
<rdar://problem/5884523>
Julien Lecomte
Comment 4 2008-04-23 13:43:32 PDT
FF, IE and Opera store the destination URL in the case of a 302. Why shouldn't Safari adopt that behavior? It seems more logical to me.
Graham Perrin
Comment 5 2008-11-01 19:09:38 PDT
(In reply to comment #4) >> temporary redirects (302, 303, 307) > FF, IE and Opera store the destination URL in the case of a 302. To me it seems most logical to * not store something temporary * store something more persistent.
Alexey Proskuryakov
Comment 6 2013-04-12 17:17:09 PDT
Mark, is this an issue in WebKit, or outside it?
Mark Rowe (bdash)
Comment 7 2013-04-12 17:20:00 PDT
This is an issue in Safari, not WebKit.
Mark Rowe (bdash)
Comment 8 2013-04-12 17:21:03 PDT
And just so no-one gets upset about the resolution, the issue is being tracked via the Radar number mentioned earlier in the comments.
Note You need to log in before you can comment on or make changes to this bug.