Recording stores

A store loads and saves the recordings. The package provides two, both backed by a file:

var store = new HarHttpRecordingStore(recordingPath);
var options = new HttpRecordingOptions { Mode = HttpRecordingMode.Record };

using var innerHandler = new SocketsHttpHandler();
using var recordingHandler = new HttpRecordingHandler(innerHandler, store, options);
using var httpClient = new HttpClient(recordingHandler);

await httpClient.GetStringAsync(new Uri(serverUrl, "/api/text"));

// Writes an HTTP Archive (HAR 1.2) file
await recordingHandler.SaveAsync();

Choose HAR to open the recordings in the tools that read HTTP Archive files, or to replay a HAR file saved by another tool. To read or write HAR files from code, see HttpArchive.

Both stores behave the same way:

• A file that does not exist is an empty store, so the first run starts from nothing.
• Saving creates the directory when needed, and is atomic: the file is written next to the destination, then moved into place, so an interrupted save cannot destroy an existing recording.
• A file that cannot be read (invalid JSON, a HAR file without log.entries, an entry without a method) throws an InvalidDataException that names the file. Delete or repair it.

Write your own store

Implement IHttpRecordingStore to keep the recordings elsewhere, for instance in embedded resources or in a database:

• LoadAsync returns every recording, or an empty list when there is none yet.
• SaveAsync receives every recording to keep and replaces what the store held.

The handler calls LoadAsync on the first request or from InitializeAsync, except in Record mode, and the store's SaveAsync from its own SaveAsync or when it is disposed with AutoSave.