Bug 138462 - Wrong referal after using back button / javascript history on webkit
Summary: Wrong referal after using back button / javascript history on webkit
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: History (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-06 03:17 PST by Thierry
Modified: 2014-11-06 04:53 PST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thierry 2014-11-06 03:17:54 PST
Steps to reproduce the problem:
1. Open chrome (or safari) in private navigation mode
2. Search for a keyword on Google
3. Click on result and navigate on 2 or 3 pages
4. Use the back button
5. See the "referer" header instruction, it will display Google as referer instead of the last consulted page

What is the expected behavior?
Sending last viewed page on referer header

What went wrong?
Sending first referer as last viewed page

Did this work before? Yes All time long, other browsers

Chrome version: 38.0.2125.111  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 15.0 r0

Makes analytics data totaly wrong, counting visits doesn't exist
Comment 1 Thierry 2014-11-06 04:52:44 PST
Not really a bug and affects all browsers, it's due to the cache restitution of the current page wich doesn't take care of you action on back button and send back the old referal of the last page.

Using Ajax to makes user navigate seriously damage your analytics data