HTTP message parsing

// I am a POST request. I told the server that I want the http: // localhost: 1538/webform1.aspx page. The httpb version I support is 1.1 post http: // localhost: 1538/webform1.aspx HTTP/1.1 export accept: text/html, application/XHTML + XML, */* expose // tell the server from which page the Referer: HT is linked TP: // localhost: 1538/webform1.aspx accept // my (browser) supports ZH-CN (Simplified Chinese) Accept-language: ZH-CN accept Content-Type: application/X-WWW-form-urlencoded ------------------------------------------------------------------------- -------------------------- // Tell the server that I (browser) is compatible with Mozilla/5.0, and the version is 11.0 (RV: 11.0) browser (IE) the typographical engine is of version 7.0 (Trident/7.0). [If Firefox corresponds to Gecko, gecko is the typographical engine used by Firefox, also called rendering engine] My OS version is Windows 7 (Windows NT 6.1) with 64-bit (wow64), // XP is Windows nt5.1, and Vista is Windows nt6.0, windows nt6.1 and Windows nt6.2 // Like gecko are the new identifier of ie11, indicating that win7 is compatible with Gecko kernel. Versions earlier than ie11 are named msieuser-AGENT: Mozilla/5.0 (Windows NT 6.1; wow64; Trident/7.0; RV: 11.0) like gecko logs // This message indicates that local data in the compressed format (gzip) can be received. After receiving the HTTP request from the browser, the server checks whether the browser supports HTTP compression; the "Accept-encoding: gzip, deflate" parameter in the HTTP header of the request sent by the browser indicates that the gzip and deflate compression algorithms are supported. when processing, the server compresses the large file and sends it back to the client. After ie receives the file, it automatically performs pressure operations on it locally. The biggest advantage of compression is that it reduces the amount of data transmitted over the network and increases the access speed of the client browser. [We can use two different compression methods: gzip and deflate; details: unzip gzip, deflate unzip HOST: localhost: 1538 unzip Content-Length: 429 ------------------------------ Always // In general, once the Web server wants the browser to send the request data, it will close the TCP connection. If the message is added with connection: keep-alive, it will be different, it will keep the connection feature // starting from HTTP/1.1. By default, keep-alive is enabled to keep the connection feature. In short, when keep-alive is enabled, after a single web page is opened, the TCP connection between the client and the server for transmitting HTTP data will not be closed. If the client accesses the web page on the server again, will continue to use this established connection // because CSS, images, and JS are all separate requests (reques). When I open this page, I suggest the server not to turn off my connection. I need to request images later. In this way, you do not need to enable a connection again in the next request. [In fact, there are several requests in a connection] connection: keep-alive keep Pragma: no-Cache items // the browser sends Cokie to the server. COOKIE: Asp. net_sessionid = itcka5su2tuqimfk3r5h0v4y _ viewstate = % too many -----------------------------------------------------------------------------------------------------