Currently, the HAR file lacks sufficient information since the responses are missing in the requests. Therefore, we need to include responses.
However, after adding the responses, the HAR file becomes very large. We need to figure out a way to reduce its size.
Suggested Solutions
Compression: Compress the file into an archive.
Selective Capture: Record only fetch/XHR (potentially WebSocket) requests, since these are relevant in 99% of cases.
Options for Customization: Introduce additional configuration options for HAR file generation, so users can dynamically decide what they need to capture.
Problem
Currently, the HAR file lacks sufficient information since the responses are missing in the requests. Therefore, we need to include responses.
However, after adding the responses, the HAR file becomes very large. We need to figure out a way to reduce its size.
Suggested Solutions
Additional Reference
In the Telegram support chat, they shared how dynamic capture for HAR files is implemented. You can check it out here: https://github.com/browserup/browserup-proxy/blob/0f28ec6e8f1423e1fdb014fded72e9278bdd083f/browserup-proxy-core/src/main/java/com/browserup/bup/proxy/CaptureType.java#L15