Differences between HTTP protocol and post and get Operations & How to Use post and get in C #

Good articles... Inniu ~ (Partition _ tables)

 

Http://www.cnblogs.com/skynet/archive/2010/05/18/1738301.html

 

Introduction

I think anyone who is familiar with the HTTP protocol can give a reason. But if I ask you what HTTP request methods are available? What is the difference between post and get? Is there a limit on the size of the data transmitted by get or post? What are the HTTP Response statuses? And how do you use it in C? If you cannot answer most of the questions clearly, this article is for you! The outline is as follows:

• 1. Http Overview
• 1.1 interaction between HTTP client and server
• 1.2. HTTP message
• 1.3. HTTP Request Method
• 1.4 HTTP response code
• 2. packet capture Analysis
• 3. Differences between post and get
• 4. Use an example to describe how to use post, get, and other operations in C #.
• 4.1. httpwebrequest
• 4.2. httpwebresponse
• 4.3 compile a winform program and open the blog homepage (with source code)

1. Http Overview

To help you remember or understand the HTTP protocol, first let's look at the HTTP protocol.Hypertext Transfer Protocol(HTTP,Hypertext Transfer Protocol) Is the most widely used network protocol on the Internet. All WWW files must comply with this standard. HTTP was designed to provide a method for publishing and receiving HTML pages.

The development of HTTP is the result of cooperation between the World Wide Web Consortium and the Internet team (Internet Engineering Task Force). They finally published a series of RFC, the most famous one is RFC 2616. RFC 2616 defines a widely used version of HTTP 1.1.

1.1 interaction between HTTP client and server

HTTP is a standard (TCP) for client and server requests and responses ).The client is an end user.,The server is a website. By using a Web browser, web crawler, or other tools, the client initiates an HTTP request to the specified port on the server (the default port is 80. (We call this client) Call the user agent ). The response server stores (some) resources, such as HTML files and images. This response server is the origin server ). There may be multiple middle layers between the user proxy and the source server, such as the proxy, gateway, or tunnel ). Although TCP/IP is the most popular application on the internet, HTTP does not stipulate that it must be used and (based on) the layer it supports. In fact, HTTP can be implemented on any other Internet protocol or on another network. HTTP only assumes that (provided by its lower-layer protocol) reliable transmission, any protocol that can provide such assurance can be used by it.

Generally, an HTTP client initiates a request to establish a TCP connection to the specified port on the server (port 80 by default. The HTTP server listens to the requests sent from the client on that port. Once a request is received, the server (to the client) sends back a status line, such as "HTTP/1.1 200 OK", and (response) message, the message body may be the requested file, error message, or other information.

The reason why HTTP uses TCP instead of UDP is that a webpage must transmit a lot of data, while TCP provides transmission control, organizes data in order, and corrects errors. Requests over HTTP or HTTPSResource Identifier(Uniform resource identifiers, or, more accurate, Uri) to identify.

The structure and interaction process between the client and the server can be shown in the following two figures:

Figure 1. Web client-server structure (the hypertext link of the Web server jumps to another server through a link on the website)

Figure 2 interaction between the Web client and the server

1.2. HTTP message

Two types of messages are used for client-to-server interaction:Request)AndResponse).

The HTTP request format is:

Figure 3. http request format

The HTTP Response format is:

Figure 4. Http response format

From the above we can see that the HTTP request and Response Message Header both contain a variable number of fields, with a blank line (Blank line) Convert allHeader field(Header) andMessage Body(Body) separated.A header field consists of a field name and a colon, a space, and a field value. The field name is case insensitive..

Packet headers can be divided into three types: requests, responses, and descriptions. Some headers (such as date) can be used for both requests and responses. The message header describing the subject can appear in the POST request and all response packets. Shows the HTTP header field:

Figure 5. HTTP header field

1.3. HTTP Request Method

HTTP/1.1 defines eight methods (sometimes called "actions") to indicateRequest-UriDifferent operations on the specified resource:

• Options
  Returns the HTTP Request Method supported by the server for a specific resource. You can also use the '*' request sent to the Web server to test the server's functionality.
• Head
  Request the server for the same response as the GET request, but the response body will not be returned. This method can obtain metadata contained in the Response Message Header without transmitting the entire response content.
• Get
  Send a request to a specific resource. Note: The get method should not be used in operations that produce "Side effects", for example, in Web application. One of the reasons is that get may be randomly accessed by web spider.
• Post
  Submits data to a specified resource for processing (for example, submitting a form or uploading a file ). Data is contained in the request body. POST requests may result in creation of new resources and/or modification of existing resources.
• Put
  Upload the latest content to the specified resource location.
• Delete
  Request server DeletionRequest-UriResource.
• Trace
  The request received by the echo server is mainly used for testing or diagnosis.
• Connect
  The HTTP/1.1 protocol is reserved for proxy servers that can change connections to pipelines.

The method name is case sensitive. When the resource for a request does not support the corresponding request method, the server should return status code 405 (method not allowed ); when the server does not recognize or support the corresponding request method, status code 501 (not implemented) should be returned ).

The HTTP server should at least implement the get and head methods. Other methods are optional. In addition to the preceding methods, the specific HTTP server can also extend the custom methods.

Security Methods

Developers should be aware that their software represents a user's interaction on the Internet and should inform users that their ongoing operations may have an unexpected and important impact on themselves or others.

In particular, for the get and head methods, except for obtaining resource information, these requests should not have any other meaning. That is to say, these methods should be considered "safe", that isThe so-called security means that this operation is used to  instead of modifying information.. The client should use other "insecure" methods, such as post, put, and delete, in special ways (usually buttons rather than hyperlinks) so that the customer can be aware of the potential responsibilities (such as capital transactions brought by a button) or the requested operation may be insecure (for example, a file will be uploaded or deleted ).

However, it cannot be assumed that the server will not produce any side effects when processing a GET request. In fact, many dynamic resources use this as their feature. The important difference here is that the user does not request this side effect, so the user should not be responsible for these side effects.

Idempotent Method

For example, if errors or expiration issues are not considered, the side effects of several requests are the same as those of a single request or there are no side effects at all, these request methods can be considered as "idempotent. The get, head, put, and delete methods both have such idempotence attributes. Likewise, because neither the protocol, options, or trace has any side effects, it is also a idempotence of course.

If the serial results of a request made up of several requests remain unchanged after the serial execution of the request or any or multiple of the requests are repeated, the request is serialized as "idempotent. However, the serial number of requests may be "non-idempotent", even if all the request methods executed in the request serial are idempotent. For example, the serial result of this request depends on a variable that will be modified during the next execution of this serial.

1.4 HTTP response code

The first line of the server program response is the status line. The status line starts with the HTTP version number, followed by three digits to indicate the response code, and finally is a readable response phrase. According to the first rule, the response can be divided into five categories:

Figure 6. Http response code

2. packet capture Analysis

Now we basically know about HTTP. Next I will use Wireshark to capture the HTTP data packets during the interaction between my computer and the blog garden server when I open the blog garden homepage. Make preparations and close some programs that may interfere with our crawling and opening the blog garden. For example, when we enter www.cnblogs.com in the browser and confirm it, we first capture the following package:

Figure 7. Open the package captured in the blog Garden

We can see that we entered www.cnblogs.com in the browser and confirmed that an HTTP request message was sent to the server: Get/HTTP/1.1. According to the HTTP message format described in section 1.2, we know that get correspondsRequest,/CorrespondingRequest-lineAnd HTTP/1.1Version Number. In addition to the request line, some header fields are sent, such as Accept, accept-language, User-Agent, accept-encoding, host, and connection. In addition, we can see that their format is:Header field name: Field ValueNote that there is a space behind the colon.

Next, let's take a look at the Response Message of the get/HTTP/1.1 request:

Figure 8. Response Message of the get/HTTP/1.1 request

The Response Message status line is: HTTP/1.1 200 OK.Expected version number, 200Response-codeAnd OKResponse-phrase. Besides the status line, some header fields are returned, such as cache-control, content-type, content-encoding, expires, last-modified, vary, and server. (We can see that the blog uses iis7.0)

The above is a get packet. Now let's take a look at a post packet. The classification information on the left is returned by the POST request when the homepage is opened.

Figure 9. Post Data Packets

We can see that post/WS/publicuserservice. asmx/getlogininfo HTTP/1.1. Except for changing get to post, other information is similar. Below we can enlarge the sending header field:

Figure 10. header field of post/WS/publicuserservice. asmx/getlogininfo HTTP/1.1

Note: I will not explain some of the header fields involved in this section here. I think here we should have a deeper understanding of HTTP.

3. Differences between post and get

8 methods are introduced in section 1.3. Get and post are the most basic and common methods. The differences between get and post methods in Form submission are summarized as follows:

• Get gets data from the server, and post transfers data to the server.
• Get adds the parameter data queue to the URL referred to by the Action attribute of the submission form. The values correspond to each field in the form one by one and can be seen in the URL. Post uses the http post mechanism to place fields in the form and their content in the HTML header and send them to the URL address referred to by the Action attribute. You cannot see this process.
• For the get method, the server uses request. querystring to obtain the value of the variable. For the POST method, the server uses request. Form to obtain the submitted data.
• The size of data transmitted by get is small and cannot exceed 2 kb (this is mainly because the URL length is limited ). The amount of data transmitted by post is large, which is generally not restricted by default. However, theoretically, the limit depends on the server's processing capability.
• Get is less secure and post is more secure. Because get data is stored in the request URL during transmission, many existing servers, proxy servers, or user proxies record the request URL to the log file, and put it somewhere, so that some private information may be seen by a third party. In addition, you can also directly view the submitted data in the browser, and some internal messages of the system will be displayed in front of the user. All post operations are invisible to users.

If method is not specified during form submission, the default value is GET request (. NET is post by default). The data submitted in form will be appended to the URL? Separated from the URL. The letter and number characters are sent as they are, but spaces are converted to "+". Other symbols are converted to % xx, XX represents the ASCII (or ISO Latin-1) value in hexadecimal notation.The data to be submitted for the GET request is placed in the HTTP Request Header, while the data to be submitted by post is placed in the object data. The data to be submitted by the get method can contain up to 2048 bytes, post does not have this restriction.. The parameters passed by post are in the doc, that is, the text transmitted by the HTTP protocol. When accepted, the parameter section is parsed. Obtain parameters. Generally, it is better to use post. The data submitted by post is implicit. Get is passed in the URL to pass some data that does not need to be kept confidential. Get is passed through parameters in the URL, and post is not.

Note: I checked the information of my predecessors on the Internet about the difference between post and get. Since I can't find the source and there are posts everywhere, I will not post the relevant website here, baidu or Google.

4. Use an example to describe how to use post, get, and other operations in C #.

Before introducing an instance, we should first introduce httpwebrequest and httpwebresponse. in C #, we use these two classes to implement sending HTTP messages to the server and receiving HTTP responses from the server.

4.1. httpwebrequest

Before designing an implementation instance, we should first introduce the httpwebrequest class-provide specific HTTP implementations of the webrequest class, And the httpwebrequest class provides support for the attributes and methods defined in the webrequest, it also supports additional attributes and methods that allow users to directly interact with servers using HTTP.

Do not use httpwebrequest constructor. Use the system. net. webrequest. Create method to initialize the new httpwebrequest object. If the Uniform Resource Identifier (URI) scheme isHttp ://OrHttps ://, Then create returns the httpwebrequest object.

The header field (headers) of the HTTP message, which is expressed as a public attribute in httpwebrequest. The following table lists the HTTP headers set by properties or methods or by the system.

If the local computer configuration specifies to use a proxy, or if the request specifies a proxy, use a proxy to send the request. If no proxy is specified, the request is sent to the server.

The httpwebrequest class mainly includes the following methods for interacting with HTTP servers:

• Abort: cancels the Internet resource request.
• Addrange: adds a range header to the request.
• Begingetrequeststream: starts an asynchronous request to the stream object used to write data.
• Begingetresponse: starts asynchronous requests to Internet resources.
• Create: initialize a new webrequest. (Inherited from webrequest .)
• Createdefault: initialize a newWebrequestInstance. (Inherited from webrequest .)
• Createobjref: creates an object that contains all the information required to generate a proxy for communication with a remote object. (Inherited from marshalbyrefobject .)
• Endgetrequeststream: endStreamThe asynchronous request of the object.
• Endgetresponse: ends an asynchronous request to Internet resources.
• Getrequeststream: GetStreamObject.
• Getresponse: returns a response from Internet resources.
• Getsystemwebproxy: returns the proxy configured in the Internet Explorer settings of the current simulated user. (Inherited from webrequest .)
• Initializelifetimeservice: gets the lifetime service object that controls the lifetime policy of this instance. (Inherited from marshalbyrefobject .)
• Registerprefix: register for the specified URIWebrequestChild. (Inherited from webrequest .)

4.2. httpwebresponse

Before designing an implementation instance, we also need to introduce the httpwebrequest class-providing specific HTTP implementations of the webresponse class. This class includes support for HTTP-specific usage of attributes and methods in the webresponse class. The httpwebresponse class is used to generate an HTTP independent client application that sends HTTP requests and receives HTTP responses.

Note:

Do not confuseHttpwebresponseAnd httpresponse class; the latter is used for ASP. NET applications, and its methods and attributes are passed through the internal ASP. NETResponseObject exposed.

You must never directly create an instance of the httpwebresponse class. Instead, use the instance returned by calling httpwebrequest. getresponse. You must call the stream. Close method or httpwebresponse. Close method to close the response and release the connection for reuse. You do not need to callStream. CloseAndHttpwebresponse. CloseBut this will not cause errors.

Public header information returned from Internet resources is exposed as a property of this class. For a complete list, see the following table. Other headers can be read as name/value pairs from the headers attribute. The following table shows the public HTTP headers that can be used through the attributes of the httpwebresponse class.

Call the getresponsestream method to return the response content from Internet resources in the form of stream.

The httpwebrequest class mainly includes the following methods to interact with the HTTP server: (compared with the httpwebrequest class, there are fewer methods)

• Createobjref: creates an object that contains all the information required to generate a proxy for communication with a remote object. (Inherited from marshalbyrefobject .)
• Getlifetimeservice: retrieves the current lifetime service object that controls the lifetime policy of this instance. (Inherited from marshalbyrefobject .)
• GetResponseHeader: Get the content of the header returned together with the response.
• Getresponsestream: gets the stream, which is used to read the response body from the server.
• Initializelifetimeservice: gets the lifetime service object that controls the lifetime policy of this instance. (Inherited from marshalbyrefobject .)

4.3 compile a winform program and open the blog homepage (with source code)

Through the introduction in the previous two sections, we have some knowledge about the httpwebrequest and httpwebrequest classes. Now we will use them to compile a small program for practice. The program interface is roughly as follows:

The function is also relatively simple, that is, you can click the "display in webbrowser" button to display the blog garden homepage in the webbrowser control below, click the "HTML source code" button to display the HTML source code of the homepage of the blog.

First, we will introduce how to implement it. By clicking the "HTML source code" button, a dialog box will pop up to display the HTML source code of the blog homepage. The core code is as follows:

Click the "HTML source code" button to display the HTML source code string getcnblogs () {string html = string on the blog homepage. empty; httpwebrequest cnbogs = (httpwebrequest) system. net. webrequest. create (txturl. text. tostring (); cnbogs. accept = "image/JPEG, application/X-MS-application, image/GIF, application/XAML + XML, image/pjpeg, application/X-MS-xbap, application/X-Shockwave-flash, application/vnd. MS-Excel, application/vnd. MS-PowerPoint, AP Plication/MSWord, application/qvod, application/qvod, */* "; cnbogs. useragent = "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; slcc2 ;. net CLR 2.0.50727 ;. net CLR 3.5.30729 ;. net CLR 3.0.30729; maln; CBA; infopath.2 ;. net4.0c ;. net4.0e; Media Center PC 6.0; Tablet PC 2.0; asktb5.6) "; cnbogs. method = "get"; httpwebresponse cnblogsrespone = (httpwebresponse) cnbogs. getresponse (); If (Cnblogsrespone! = NULL & cnblogsrespone. statuscode = httpstatuscode. OK) {using (streamreader sr = new streamreader (cnblogsrespone. getresponsestream () {html = sr. readtoend () ;}} return HTML;} private void btngethtml_click (Object sender, eventargs e) {MessageBox. show (getcnblogs ());}

In fact, in this process, we enter the blog garden website in a browser to open the website with the same effect. However, here we implement it through the objects of the httpwebrequest class and httpwebrequest class.

However, by clicking the "display in webbrowser" button, the function of displaying the homepage of the blog garden is similar in the webbrowser control below, it is only displayed in the webbrowser control. Here I encapsulate some common http-related operations into a namespace helper for future use, which is essentially the same as above. Click to download the source code of the entire project.

My source code is still relatively simple, but I simply implemented the interaction between the httpwebrequest class and the HTTP server. More comprehensive functions are coming soon.

 

Additional instructions: For URL length restrictions, the URL of IE can contain a maximum of 2083 characters (half width), and The get can contain a maximum of 2048 characters. However, RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1 does not limit the maximum URL length.

 

Refer:I have read many articles when writing this article.

• Wikipedia (HTTP), http://zh.wikipedia.org/zh-cn/HTTP
• Msdn, http://msdn.microsoft.com/zh-cn/library/8y7x3zz2%28v=VS.80%29.aspx
• Msdn, http://msdn.microsoft.com/zh-cn/library/system.net.httpwebresponse%28VS.80%29.aspx
• TCP/IP protocol details 3

There are two ways to submit a single form. One is the get method and the other is the POST method. Check the following code to understand the differences between ASP. NET get and post:

The following is a code snippet: <Form ID = "form1" method = "get" runat = "server"> <Div> Your name <asp: textbox id = "name" runat = "server"> </ASP: textbox> <br/> <Br/> Your website <asp: textbox id = "website" runat = "server"> </ASP: textbox> <br/> <Br/> <Br/> <Asp: button id = "button1" runat = "server" text = "send"/> <br/> <Br/> <Br/> Learn request and response usage <br/> <Br/> <Br/> </Div> </Form> <Form ID = "form2" method = "Post" runat = "server"> <Div> Your name <asp: textbox id = "name2" runat = "server"> </ASP: textbox> <br/> <Br/> Your website <asp: textbox id = "website2" runat = "server"> </ASP: textbox> <br/> <Br/> <Br/> <Asp: button id = "button2" runat = "server" text = "send"/> <br/> <Br/> <Br/> Learn request and response usage <br/> <Br/> <Br/> </Div> </Form>

From the URL, we can see the difference between ASP. NET get and post. So how can we program the data reception?

There are 1st types of data to be transmitted using the get method:

The following is a code snippet: Protected void page_load (Object sender, eventargs E) { String id = request. querystring ["name"]; String website = request. querystring ["website"]; Response. Write (ID + "<br>" + website ); Response. Write ("you are using" + request. requesttype + "Data Transmission "); }

2nd. Write Method for receiving data transmitted using the POST method:

The following is a code snippet: Protected void page_load (Object sender, eventargs E) { String Id2 = request. Form ["name2"]; String website2 = request. Form ["website2"]; Response. Write (Id2 + "<br>" + website2 ); Response. Write ("you are using" + request. requesttype + "Data Transmission "); } String ID4 = request ["name4"]; String website4 = request ["website4"]; Response. Write (ID4 + "<br>" + website4 );

3rd types of code that accepts both the get and post methods for data transmission:

Write method String ID3 = request. Params ["name3"]; String website3 = request. Params ["website3"]; Response. Write (ID3 + "<br>" + website3); write B String ID4 = request ["name4"]; String website4 = request ["website4"]; Response. Write (ID4 + "<br>" + website4 );

In form submission, the difference between ASP. NET get and post methods is summarized as follows:

1. Get is to get data from the server, and post is to send data to the server.

2. Get is to add the parameter data queue to the URL referred to by the Action attribute of the submission form. The values correspond to each field in the form one by one and can be seen in the URL. Post uses the http post mechanism to place fields in the form and their content in the HTML header and send them to the URL address referred to by the Action attribute. You cannot see this process.

3. For the get method, the server uses request. querystring to obtain the value of the variable. For the POST method, the server uses request. Form to obtain the submitted data.

4. The data volume transmitted by get is small and cannot exceed 2 kb. The amount of data transmitted by post is large, which is generally not restricted by default. Theoretically, the maximum size of IIS4 is 80 KB, and that of iis5 is 100kb.

5. Low get security and high post security. However, the execution efficiency is better than the POST method.

Suggestion:

1. The get method is more secure than the POST method. If it contains confidential information, we recommend that you use the post data submission method;

2. We recommend that you use the get Method for Data Query. We recommend that you use the post Method for Data addition, modification, or deletion.