> ## Documentation Index
> Fetch the complete documentation index at: https://help.dingtalk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Import HAR Files

> Walks through the complete process of exporting a HAR file from a browser and importing it for analysis to troubleshoot resource-loading issues on YiDA pages under specific network environments.

Mid- and back-office systems typically enforce strict permission controls, which can make troubleshooting production issues difficult. In most cases, start by investigating resource-related problems.

## An Example

A user reported: "I have an external system that works fine on the internal network, but issues appear when I disconnect from the VPN." See the screenshots below:

How should you investigate this issue?

## The Typical Approach

You need to obtain links, request permissions, gather various prerequisites, and then start debugging. By the time you finish all these steps, a significant amount of time has already passed.

## How to Solve It Using a HAR File

### Step 1: Ask the User to Download a HAR File. How Is It Downloaded?

1. On the page where the issue occurs, follow the actions shown in the GIF below.

2. The downloaded `***.har` file is what you need. Send this file to the developer for analysis. (Avoid using this method on pages containing sensitive information, as it may cause information leakage.)

### Step 2: How Does the Developer Inspect Network Requests Through the HAR File?

Open `about:blank` and upload the file in the same area shown in the download screenshot above.

## What Was the Root Cause in This Example?

Based on the information in the HAR file, you can see that requests were sent to the internal domain `internal.example.com`, and the version used was `0.4.0` (the daily build). Switching to the production version resolves the issue.

## [Links](https://developers.google.com/web/tools/chrome-devtools/network/reference)
