How do I generate a HAR file?
A HAR capture (HTTP Archives) records your browser's requests and responses with the GitBook Application, allowing our support team to investigate the issues you are experiencing further.
You need to save two files locally: a HAR file, and a console log.
In Chrome, go to the page in GitBook where you're experiencing the issue.
Select ⋮ at the top right of your browser window to open Chrome settings.
Select > More tools > Developer tools. Developer tools opens as a panel at the side or bottom of Chrome.
Select the Network tab.
Select the Preserve log checkbox.
Confirm the red circle is visible at the top left of the Network tab — this means recording has started. If the circle is black, select it to start recording.
Refresh the page and reproduce the issue.
Select the download icon (↓) in the Network tab toolbar to save all requests as a HAR file.
Select the Console tab.
Right-click anywhere in the console and select Save as….
Name the file
Chrome-console.log.Reply to your case with both files as shared links.
In Firefox, go to the page within GitBook where you are experiencing trouble.
Click the Firefox menu (Three horizontal parallel lines) at the top-right of your browser window.
Select web developer > network.
The developer tools window opens as a docked panel at the side or bottom of Firefox.
Click the network tab.
Select persist logs.
Refresh the page and reproduce the problem while the capture is running.
After reproducing the issue, right-click any row of the activity pane and select Save all as HAR.
Select the console tab.
Right-click any row and select select all.
Paste the content in a text file and name it console-log.txt.
Send both files as shared links in a reply to your case.
In Safari, go to the page within GitBook where you are experiencing trouble.
In the menu bar at the top, click Develop and select Show Web Inspector.
Click the console tab and select preserve log.
Go back to the network tab.
Refresh the page and reproduce the problem while the capture is running.
After successfully reproducing the issue, right-click any row of the activity pane and select export HAR.
Click the console tab.
Right-click any row and select select all.
Paste the content in a text file and name it console-log.txt.
Send both files as shared links in a reply to your case.
In Internet Explorer, go to the page within GitBook where you are experiencing trouble.
Click the gear icon in the top right.
Select F12 developer tools.
Click the network tab.
Clear the entries on the navigate option, which is selected by default. The icon looks like a blue arrow with a red X.
The green play button (start profiling session) should be selected by default. This means the capture function is running.
Refresh the page and reproduce the problem while the capture is running.
Once you have reproduced the issue, click the export as HAR icon. The icon looks like a floppy disk.
Click the console tab.
Right-click any row and select copy all.
Paste the content in a text file and name it console-log.txt.
Send both files as shared links in a reply to your case.
In Edge, go to the page within GitBook where you are experiencing trouble.
At the top-right of your browser window, click the Edge menu (⋮)
Select developer tools.
Click the network tab.
Clear the entries on the navigate option, which is selected by default. The icon looks like a blue arrow with a red X.
The green play button (start profiling session) should be selected by default. This means the capture function is running.
Refresh the page and reproduce the problem while the capture is running.
Once you have reproduced the issue, click the export as HAR icon. The icon looks like a floppy disk.
Click the console tab.
Right-click any row and select copy all.
Paste the content in a text file and name it console-log.txt.
Send both files as shared links in a reply to your case.
Last updated
Was this helpful?