Re: [Archive-access-discuss] Can Wayback cope withwindow.open('{URL}','_self'); ?

[Jackson, A. <And...@bl...>]

We're using the server-side rewriting engine, and it's not catching this
case. We'll probably experiment with injecting JavaScript to override
the window.open function so that there's a re-write in the function
invocation chain, but would be interesting to know if anyone has already
tried this or other approaches.

 

Thanks again,

Andy

 

From: Bjarne Andersen [mailto:bj...@st...] 
Sent: 05 December 2012 12:04
To: Jackson, Andrew; arc...@li...
Subject: SV: [Archive-access-discuss] Can Wayback cope
withwindow.open('{URL}','_self'); ?

 

I have a feeling that this is not possible when using the broswer-based
rewriting engine. 

You would need to use either the serverside rewriting (I never tried
that) or proxy based replay (which we allways use at Netarchive.dk to
gain the most optimal replay) to catch a thing like this.

 

Best

Bjarne

 

Fra: Jackson, Andrew [mailto:And...@bl...] 
Sendt: 5. december 2012 12:32
Til: arc...@li...
Emne: [Archive-access-discuss] Can Wayback cope with
window.open('{URL}','_self'); ?

 

Hi All,

 

We're having problems with live-leakage, in that if you go to:

 

http://www.webarchive.org.uk/wayback/archive/20081212111012/http://www.w
oolworthsgroupplc.com/site/woolworths.asp
<http://www.webarchive.org.uk/wayback/archive/20081212111012/http:/www.w
oolworthsgroupplc.com/site/woolworths.asp> 

 

Then some JavaScript immediately redirects you to the live version of
the site:

 

window.open('http://www.woolworths.co.uk/','_self');

 

Does anyone know if there is any existing code in Wayback one can use to
override this behaviour?

 

Thanks for your time,

Andy Jackson

 

--

Andrew Jackson

Web Archiving Technical Lead

The British Library

 

Tel: 01937 546602

Mobile: 07765 897948

Web: www.webarchive.org.uk

Twitter: @UKWebArchive