Cause analysis of aborted in result of HttpWatch [map]

We sometimes see values for non-HTTP status code (status codes) in the process of Web debugging using HttpWatch, for example: (aborted).

　　

(aborted) is one of the three non-HTTP status code defined in HttpWatch, which is used in HttpWatch to indicate that the server has not returned any Status code to the request issued:

• L (aborted)
• L (Cache)
• L error_*

The meaning of the last two values is obvious. (cache) is used to indicate that the content returned in the request is not retrieved from the server but is retrieved directly from the browser's cache. Therefore, the server does not return status Code if there is no real exchange of information with the server. The other is error_*, which is used to indicate that an error occurs when the Internet Explorer requests data to cause the request to fail.

(aborted) is more complex than the above two, which occurs when IE begins processing a request for a specified URL, but the request is aborted. The following are typical examples of several requests being aborted:

1. During a page load (for example, a picture is being downloaded), the user taps a link in the page or clicks the browser's Stop button. In this case, ie aborts all activation status requests, and the result of these aborted requests in HttpWatch is displayed (aborted).
2. When the user triggers an hover event for an element (hover requests), and the mouse moves out of the zone where the hover event is bound during the request. In this case, requests that have not yet been completed will be forcibly discarded by IE.
3. Sometimes developers use Ajax to request data, but instead of waiting for the server to return data and continue to do other processing, requests that should be received will be forcibly discarded by IE.

In fact, the core of the above question is "will the request received by the server be (forcibly) aborted?" The answer to this question depends on when the request will be discarded. By looking at HttpWatch's timing chart, you can clearly see when the request was canceled.

Here is an example of a request being aborted during a connection:

　　

In the example above, the server does not receive a request from the client because the request has not yet reached the send stage

The following aborted scenario occurs when IE is waiting for the server to return the request results

　　

The three types of information that are defined in HttpWatch are primarily intended to reflect some of the information that the user interacts with the site (non-status Code), rather than to indicate that the request has been wrong

Cause analysis of aborted in result of HttpWatch [map]