Limit WARC header/content capture to current tab only

Open machawk1 opened this issue 12 years ago • 3 comments

Currently, asynchronous requests from other tabs pollute the WARC if they occur during the WARC creation process.

May 22 '13 03:05 machawk1

This might be fixed by limiting the capture to the current tab in the response and request capture filters but requires a bit more testing, which should be easy enough by keeping some other site that extensively uses Ajax open in another tab.

May 23 '13 01:05 machawk1

For testing, throw this page ( http://warcreate.com/tests/bug7.html ) up in a tab, new tab, enable WARCreate with a simple HTML page, and note the noise included in the WARC.

Aug 13 '14 19:08 machawk1

Is this the right functionality or should it be "all of the tabs the user visited with WARCreate enabled."

Aug 13 '14 20:08 machawk1