4 ms·

It'd be neat to extend the warc format and tooling to support cached http responses for things like REST endpoints. Then you could make sure everything you did

It'd be neat to extend the warc format and tooling to support cached http responses for things like REST endpoints. Then you could make sure everything you did in a session is recorded for later use. From the specification it would appear fairly straightforward once an approach was chosen... Here's the relevant extract from the warc spec that informed my difficulty estimate - "The WARC (Web ARChive) file format offers a convention for concatenating multiple resource records (data objects), each consisting of a set of simple text headers and an arbitrary data block into one long file." Edit: Upon 2 minutes of reflection I think the way to go for what I'm envisioning is some kind of browser session recording -> replayable archive solution.

uniqueuid 4y ago
Although this is a nice idea, it's extremely difficult to get it completely right. Consider a SPA where navigation happens via xhr or similar requests and updates are json that's patched into the DOM. Even browsers have a hard time figuring out how to make this a coherent session. Now with warc, you get a single record per transfer, i.e. every json file, every image, every css is an individual record. It's completely up to the client/downstream tech to re-assemble this into a coherent page. If you want to go down that road, my best suggestion would be to start with a browser's history - that's probably the most solid version of a session that we have right now.
nikisweeting 4y ago
ArchiveWeb.page + ReplayWeb.page are able to achieve what you're describing.