今天发现httpwacher出现aborted，查了下：
he result column in HttpWatch may sometimes display the value (Aborted) instead of an HTTP status code:
(Aborted)
(Aborted) is one of three pseudo status codes that are used in HttpWatch to display information about HTTP requests that did not receive a status code from the server:
* (Aborted)
* (Cache)
* ERROR_*
The last two values are fairly straight forward. The (Cache) result is displayed when content is read directly from the browser cache with no network round-trip. If there’s no network round-trip, there’s no HTTP status code returned from the server. And the ERROR_* result (e.g. ERROR_INVALID_URL) is used when a request fails to complete because an error was detected by Internet Explorer.
The (Aborted) value is more complex in its origin. It occurs when IE has started to process the request for a URL (e.g. to download an image), but then decides to cancel the operation. Here are some examples of when this can occur:
1. If you click on a link or bookmark while a page is downloading, or click on IE’s Stop button, you will see that IE cancels any requests which are still active and HttpWatch shows the (Aborted) result.
2. A CSS rollover image on a page will start a request when the mouse pointer is moved into its active area. If the mouse pointer quickly moves away again, IE may abort the request if it has not already completed.
3. Sometimes javascript is used to fire off requests for background tasks or to gather statistics on a page. Often this can lead to aborted results if the javascript does not wait for the response to be received from the server.
A common question is “Will our server receive requests that ended up being aborted?”. The answer is that it depends when the request was aborted. By looking at the timing chart in HttpWatch you can determine how far the request was through its normally processing cycle before it was cancelled.
Here’s an example of a request that was aborted while a connection was being made:
Aborted while connecting
The server would not have received the HTTP request message in this case, because the Send state was not reached.
The request shown below was aborted when IE was awaiting a response and therefore the request would have been delivered to the server:
Aborted while waiting
The presence of an (Aborted) entry in an HttpWatch log file is often just a consequence of the way that the user is interacting with a web site, rather than an indication that something has gone wrong.
来源：http://www.sanotes.net/html/y2008/165.html
he result column in HttpWatch may sometimes display the value (Aborted) instead of an HTTP status code:
(Aborted)
(Aborted) is one of three pseudo status codes that are used in HttpWatch to display information about HTTP requests that did not receive a status code from the server:
* (Aborted)
* (Cache)
* ERROR_*
The last two values are fairly straight forward. The (Cache) result is displayed when content is read directly from the browser cache with no network round-trip. If there’s no network round-trip, there’s no HTTP status code returned from the server. And the ERROR_* result (e.g. ERROR_INVALID_URL) is used when a request fails to complete because an error was detected by Internet Explorer.
The (Aborted) value is more complex in its origin. It occurs when IE has started to process the request for a URL (e.g. to download an image), but then decides to cancel the operation. Here are some examples of when this can occur:
1. If you click on a link or bookmark while a page is downloading, or click on IE’s Stop button, you will see that IE cancels any requests which are still active and HttpWatch shows the (Aborted) result.
2. A CSS rollover image on a page will start a request when the mouse pointer is moved into its active area. If the mouse pointer quickly moves away again, IE may abort the request if it has not already completed.
3. Sometimes javascript is used to fire off requests for background tasks or to gather statistics on a page. Often this can lead to aborted results if the javascript does not wait for the response to be received from the server.
A common question is “Will our server receive requests that ended up being aborted?”. The answer is that it depends when the request was aborted. By looking at the timing chart in HttpWatch you can determine how far the request was through its normally processing cycle before it was cancelled.
Here’s an example of a request that was aborted while a connection was being made:
Aborted while connecting
The server would not have received the HTTP request message in this case, because the Send state was not reached.
The request shown below was aborted when IE was awaiting a response and therefore the request would have been delivered to the server:
Aborted while waiting
The presence of an (Aborted) entry in an HttpWatch log file is often just a consequence of the way that the user is interacting with a web site, rather than an indication that something has gone wrong.
来源：http://www.sanotes.net/html/y2008/165.html
作者：jackxiang@向东博客 专注WEB应用 构架之美 --- 构架之美，在于尽态极妍 | 应用之美，在于药到病除
地址：https://jackxiang.com/post/2379/
版权所有。转载时必须以链接形式注明作者和原始出处及本声明！
[转]Mysql Source导入乱码问题
PHP 5.2.12 发布 修复60多个bug评论列表
