I'm working on a project that specifically requires Chrome compatibility. One issue was related to changing Wagtail's WAGTAILDOCS_SERVE_METHOD to serve_view, functionally meaning that instead of redirecting document requests to the storage bucket, Wagtail will instead consume the document from the bucket and stream it to the client.

While testing this process I needed to inspect the response headers for the file download request, but the developer console wasn't showing any network traffic. I don't really know the details about why, and I don't care, but I needed the headers, and using curl wasn't working, because I don't have privileges to generate a JWT via this client's particular cloud platform.

Enter chrome's net-export functionality: chrome://net-export/. This allowed me to capture all network traffic in the entire browser. I started the capture, clicked the link, then stopped the capture, finally using Google's netlog-viewer app to visualize the data and locate the file download response headers.