Bug 50415 - Mismatched address bar URL and page contents when using back after pushState and location.replace
Summary: Mismatched address bar URL and page contents when using back after pushState ...
Status: RESOLVED DUPLICATE of bug 49654
Alias: None
Product: WebKit
Classification: Unclassified
Component: History (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-02 15:44 PST by Mihai Parparita
Modified: 2010-12-20 11:01 PST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mihai Parparita 2010-12-02 15:44:05 PST
Test case: http://persistent.info/webkit/test-cases/pushstate-https/test.html. To reproduce:
1. Click either link (which onclick does a history.pushState followed by a location.replace)
2. Press the back button

The page (google.com) is still displayed, but with the URL of the testcase. 

This may have the same cause as bug 49654.
Comment 1 Mihai Parparita 2010-12-06 10:19:48 PST
Abishek, does this have any security implications? As far as I can tell, an attacker could get the location bar to show a URL under his control while the page contents are not, so it's not exploitable for spoofing, but I might be missing something.
Comment 2 Abhishek Arya 2010-12-06 10:29:07 PST
Thanks Mihai. This does looks like it will be fixed by Johnny's patch. Johnny, can you please double check. I don't see a security issue here unless page contents are controllable.
Comment 3 Johnny(Jianning) Ding 2010-12-06 11:07:05 PST
(In reply to comment #2)
> Thanks Mihai. This does looks like it will be fixed by Johnny's patch. Johnny, can you please double check. I don't see a security issue here unless page contents are controllable.

I am re-thinking about my patch in bug 49654 according to darin's comments, it may need to take few days to find another solution.
Comment 4 Mihai Parparita 2010-12-20 11:01:53 PST
Darin is working on bug 49654, and is pretty sure that his fix will take care of this too.

*** This bug has been marked as a duplicate of bug 49654 ***