Grab Bag Tool-HttpWatch

HttpWatch is a powerful web data analysis tool, integrated in the IE toolbar, the main features are web snippets, cookies management, cache management, message hair Send/Receive, character query, post data, directory management functions and report output. HttpWatch is a software that collects and displays deep information, it can display the Web page request and the response log information simultaneously without proxy server or some complicated network monitoring tools, even display the browser cache and the IE Exchange information, integrates in the IE toolbar. (HttpWatch tools need to download and install, here is not said, direct search Baidu OK)

HTTP Basics HTTP message Format

　　When a user accesses a URL address by using a browser, submits the form data, the browser generates a request message to the server, and the server receives the request and returns the resulting response message to the browser. The request information sent by the browser and the response information returned by the server are collectively known as HTTP messages. HTTP messages have a strict format.

A complete request message consists of a request line, a number of message headers, and entity content, some of which are optional, separated by a blank line between the message header and the entity content, and the contents of the HTTP request message:

(Request-line) GET/Get. Do? prod=wmail_lbp&ver=1&[email protected]163. com&domain=163. com&mobuser=0&callback=themehandler.callback&rnd=0.13562542999267713http/1.1Accept Application/javascript, */*; q=0.8accept-encoding gzip, deflateaccept-language zh-cnconnection Keep-alivecookie starttime=; logType=Ho St Ir3.mail.163.comrefererhttp://mail.163.com/user-agent mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; trident/5.0)

HTTP Request message Content

A complete response message includes a status line, several message headers, and the entity content. As with the request message, some of the message headers and entity contents in the response message are also optional, separated by a blank line between the message header and the entity content. The following is the content of the HTTP response message:

(Status-line)    http/1.1  okconnection    Keep-alivecontent-length    25037 Content-type    application/json;charset=utf-8Date    2017  £ º  gmtserver    nginxvary    Accept-Encodingx -cache from     ngx118-192.163. com

HTTP Response message content

HTTP requests and HTTP response headers are both used to describe the HTTP message itself, often referred to as meta-information, the message header is equivalent to the server and the browser password instructions, the main implementation of the HTTP client and server conditional request and response.

Typically, the message header is divided into 4 categories: Information headers, request headers, response headers, and entity headers:

1) General Information header: that can be used to request information, but also for responding to messages, but not related to the content of the transferred entity, such as date, pragma.

2) Request header: Used to pass an additional message to the server in the request message, mainly including the type of data that the client can accept, the compression method, the language, and the cookie information that is kept on the client computer and the hyperlink source address that made the request.

3) Response header: Used to pass additional information to the client in the response message, including the name of the service program, how the client is required to authenticate, the new address to which the requested resource has been moved, and so on.

4) Entity header: Used as meta-information for entity content, describes the attributes of entity content, including the type of entity information, length, compression method, time of last modification and validity of data.

The request line for the request message includes 3 parts: The request method, the resource path, and the version of the HTTP protocol used, separated by spaces, with the syntax in the following format:

Request Way Resource Path HTTP version number <CRLF>

Where <CRLF> represents a combination of carriage return and newline two characters.

The status line of the response message includes 3 parts: The version number of the HTTP protocol, an integer code that indicates success or failure (status code), and textual information describing the status code, separated by a space between the sections, with the following syntax:

HTTP version Number status code reason description <CRLF>

request Grid for the HttpWatch tool

After the installation of the Ie-tool to start the HttpWatch, enter the address and click the Record button to start recording, click the Stop button to stop recording, 1, recorded 163 mailbox logon action

Figure 1 (Request grid diagram)

Started: Relative start time refers to the time that the URL that is accessed next is opened relative to the first URL, such as http://mimg.127.net/copyright/year.js The HTML http://mail.163.com/ page 0.006s is only executed .

Time Chart: The elapsed scale graph, which is a graph of how long it takes to complete parts of the request answer process.

Time: How long the request has been consumed.

Sent: The number of bytes sent to commit the request.

Received: The number of bytes returned by the server after the request is committed.

Method: The way to submit the request.

Result: The outcome of the request processing.

Type: The types of content returned by the server.

URL: The URL address of the request.

　　During the test, the main focus is on the values of time, Received, result three items, when the request takes longer to pay attention to the time-consuming request, because during the entire business response time, the time-consuming request is most likely to need tuning; Received is the number of bytes returned, The need to pay attention to the large number of bytes returned during testing, because the large number of bytes returned, can affect the time-consuming of the entire request, which is also the focus of the tuning needs to be focused; result is the state of the request response, which requires attention to a value whose response status is not 200, and only 200 of the request response State is correct The others are abnormal, and if the request has an exception, the transaction is likely to fail, which directly affects the success rate of the transaction.

request View of the HttpWatch tool

The request view content details each requested information, mainly including the following:

One, as shown in overview,2

Figure 2 (Overview content)

Display URL: The URL representing the request;

Started at: Indicates the start time of the request;

Submit form: Indicates that the form is submitted to the URL, only the post operation will be available;

CONNECTE: Represents the TCP connection operation;

HTTP Request: Indicates that a request was sent out;

HTTP Response: Indicates that an answer is retracted;

Read cache: Indicates that the request was to read the reply message from the Cache;

Second, time chart,3 is shown

Figure 3 (Time chart chart)

Shows the time taken for each time fragment in a request answer process. The time fragment required for a complete request response process is as follows: Blocked->dnslookup->connect, Send->wait->receive.

Each time fragment has the following meanings:

Blocked (blocking): The time of blocking mainly includes preprocessing time (such as cache lookup) and network queue wait time, the most important cause of blocking is downloading the picture on the page;

Dns Lookup (Domain name Interpretation): The Domain name interpretation time is mainly the host name (such as www.google.com) into the corresponding IP address (216.239.59.99) time, when the URL address, the address itself can not be directly accessed, it needs to correspond to the corresponding IP address to access;

Connect: Connection time refers to the time it takes to establish a TCP connection with a Web server (or proxy server), a secure HTTPS connection should contain the process of SSL handshake, keep the system in a state of being connected, and save the time to duplicate the TCP connection creation

Send: Sending time is the time it takes to send an HTTP request to the server from the client, and the size of the data sent will affect the time sent, such as the time it takes to upload the file is longer;

Wait: The waiting time is the time the server responds to the request, including the network latency and the time it takes the server to process the request;

Receive (receive): The time taken by the server to return data to the client, which is affected by the size of the returned message content, the network bandwidth, and the HTTP compression ratio;

Cache read: Read cache time refers to the time the content is read from the browser cache;

Three, the headers,4 show

Figure 4 (contents of headers)

The contents of Headers sent are as follows:

(Request-line): includes the HTTP submission request method, HTTP version, and URL sub-path;

Accept: Acceptable file types;

Accept-encoding: The type of content encoding that is acceptable in addition to plain text;

Accept-language: The type of language acceptable for return data;

Connection: Specifies how the connection is handled after the response of the request has been completed;

Cache-control: Specifies the caching mechanism that requests and responses follow;

Location: Used to redirect the recipient to a new URL address;

Host: The hostname of the request connection;

The contents of Headers received are as follows:

(Status-line): Includes the status Code and HTTP version information of the HTTP request;

Connection: Specifies how the connection is handled after the response of the request has been completed;

Cache-control: Specifies the caching mechanism that requests and responses follow;

Content-language: The language type of content data;

Content-length: The content length of the transmission;

Content-type: Type of content data (Mini type);

Last-modified: The last revision time to save content on the server;

Expires: The expiration time when the content data is cached;

Four, the cookies,5 show

Figure 5 (contents of the cookie)

The name of the Cookie Name:cookie;

Direction: Indicates whether the cookie was sent by the client to the server or received from the server;

The content of Value:cookie;

Path: The route of the site where the cookie resides;

Domain: Displays the name or hostname to which the cookie belongs;

Expires: The cookie expires when the cookie value is deleted when the browser is closed;

V. cache,6, as shown in

Figure 6 (content of the cache)

URL in cache?: whether the content is written to the browser cache;

Expires:cache expiration date and time;

Last modification: When the cache content is stored or updated, the change date will be modified to the nearest date;

Last Cache Update:cache content is updated in the most recent time;

Last Access: Time of the most recent cache read;

ETag: Used to match the entity on the server, using the method of fuzzy matching;

Hit count: The number of times the cache content was read;

Six, Query string,7 shows

Figure 7 (contents of Query string)

Query string is a way to pass a parameter through a URL, usually in the following format: ...? Name1=value1&name2=value2&, .....

The Query string content can display all the parameter names and corresponding values in the current URL, and the corresponding URL for Figure 7 is as follows:

Http://ir3.mail.163.com/get.do?prod=wmail_lbp&ver=1&uid=****@163.com&domain=163.com&mobuser=0 &callback=themehandler.callback&rnd=0.639472691290614

As shown in post data,8, the data information requested by the post is displayed, where MIME Type:application/json refers to the encoding of the post-submitted data.

Figure 8 (content of POST data)

As shown in content,9, displays the HTTP response information received, including the type of MIME, the total number of bytes and whether the content is downloaded from the service or read from the cache, if the HTTP is compressed, it should also show the way of compression, compressed file size and compression ratio.

Figure 9 (content)

Nine, stream,10, mainly shows the content sent by the client and the content returned by the server. The left side shows what the client sends, shows the size of the data stream and which server to send, the number of bytes sent is 2,173 bytes, the server IP address is 220.181.12.208, and the port number is 80. The right side shows what the server returns, including the number of bytes returned and the IP address returned to the client.

Figure ten (Stream content)

On the left is the request submitted by the client to the server, as follows:

Get/entry/cgi/ntesdoor?df=loginjustnowmail163&funcid=loginjustnow&iframe=1 Http/1.1:get represents the request method, '/' Represents a URI (Uniform Resource Identifier, which is a common resource identifier for accessing available resources on the web), and http/1.1 represents the Protocol and protocol version used;

Accept: Represents the type of the accepted return data, */* means that all data types are accepted;

Referer: Represents a URL address (such as http://mail.163.com/) that represents a request made from that address;

Accept-language: The language that accepts the returned data, such as ZH-CN, that accepts the returned data language as Chinese;

Accept-encoding: Indicates that the browser can accept content encoded in addition to plain text, such as gzip compression, deflate compressed content;

User-agent: Identifies the client browser type and related version information;

Host: Identity address;

Connection: Indicates the connection state, such as keep-alive indicates the connection state of keeping TCP;

The content on the right is the data content returned by the server to the client, as follows:

http/1.1: Indicates the Protocol, protocol version, the status of the request;

Date: Indicates the day the HTTP message was sent;

Expires: Indicates the validity period of the entity;

Content-type: Indicates the server return request type, such as text/html;

Last-modified: Indicates the date and time when the requested resource was last modified;

Age: Indicates the cache time of the HTTP accept Request Operation response;

Ten! As shown in warnings,11, a warning is displayed for a single request, with a detailed description of the warning ID, warning type, and warning about the type of warning: performance (performance), security, and functional (features)

Figure 11 (! Warnings's content)

Summary View of HttpWatch tools

Summary can display a page or a set of page request summary information, 12:

Figure (Summary-network's content)

Elapsed time: Indicates how long it takes to complete all requests from the beginning of the first request to the current page, in units of S, and obviously the smaller the value, the better;

Network Round Trips: Indicates the number of times a request is submitted to the requested information to return a shared Web server, as well as the smaller the value;

Downloaded Data: The number of bytes downloaded, in bytes, and the smaller the value, the better;

Uploaded data: Indicates the number of bytes sent to the server side, and the smaller the value is, the better;

HTTP Compression Savings: Indicates the number of bytes reduced after HTTP data compression;

DNS Lookups: Indicates the number of times the domain name is resolved to the corresponding IP address (such as resolving the domain name www.google.com to 72.14.221.103);

TCP Connects: Represents the number of times a TCP connection is established, which is used to indicate the ability of the server to remain connected, and the smaller the value is, the better;

Total HTTPS Overhead: The number of requests that require encryption in all submission requests;

Average HTTPS Overhead per request: Average HTTP value for each requested, if this value is too high it is likely due to incorrect server.

Page events, shown in Content 13, represent the events that are requested by the pages and the time that each event corresponds to, and the composition of the time blocks is described in detail in the date Chart section of the request view, which is not covered here.

Figure (Content of page events)

Timings content 14, which indicates the time spent in each phase of the URL request, is not mentioned above.

Figure (Timings's content)

Status codes, shown in content 15, mainly shows the state code returned by the server after the client submits the request.

Figure (Status Codes content)

Errors and warning content is primarily a display of error and warning information that occurs during the request process.

other features of the HttpWatch tool

In addition to the features described above, there are two other functions, filter and find, 16, 17:

Figure (Filter dialog box)

Figure (Find dialog box)

Grab Bag Tool-HttpWatch