Tags: webrecorder/browsertrix-crawler
Tags
fix unloading, fix hardcoding to be added to list bump to 1.5.0-beta.1
Ensure partial responses are not written (#721) various fixes for streaming, especially related to range requests - follow up to #709 - fix: prefer streaming current response via takeStream, not only when size is unknown - don't serialize async responses prematurely - don't serialize 206 responses if there is size mismatch
fix cookie not being passed to replay regression - for now, add x-wabac-preset-cookie header for quick fix (same as AWP) - more permanent fix will involve fixing warcio.js indexing to include the header - fix replay of X captures and other pages requiring cookies
various edge-case loading optimizations: (#709) - rework 'should stream' logic: * ensure 206 responses (or any response) greater than 25M are streamed * response between 5M and 25M are read into memory if text/css/js as they may be rewritten * responses <5M are read into memory * responses with unknown size are streamed if a 2xx, otherwise read into memory, assuming error code responses may lack status codes but otherwise are small - likely fix for issues in #706 - if too many range requests for same URL are being made, try skipping/failing right away to reduce load - assume main browser context is used not just for service workers, always enable - check false positive 'net-aborted' error that may actually be ok for media, as well as documents - improve logging - interrupt any pending requests (that may be loading via browser context) after page timeout, log dropped requests --------- Co-authored-by: Tessa Walsh <tessa@bitarchivist.net>
PreviousNext