Home >Backend Development >PHP Tutorial >PHP uses ajax data to submit post and summary of common methods of post, ajaxpost_PHP tutorial

PHP uses ajax data to submit post and summary of common methods of post, ajaxpost_PHP tutorial

WBOY
WBOYOriginal
2016-07-13 10:14:25832browse

php uses ajax data to submit post and summary of common methods of post, ajaxpost

The example in this article describes the common methods of PHP using ajax data to submit posts and posts. Share it with everyone for your reference. The specific method is as follows:

In many cases, there will be no problem when we use ajax, but sometimes we encounter the problem of incomplete ajax data submission post. Here is an example for everyone to analyze.

The following is a standard ajax request code. Under normal circumstances, there will be no problems. However, problems may occur under certain circumstances, such as username=fdas&321, or the & symbol appears in the parameter value. After N times of testing, we found that all the data was transmitted, but the printed data was half-cut. Finally, we carefully observed the header information and found that the transmitted header was wrong. The problem was located in js, and we found that the method of string splicing would cause this problem username =fdas&321&password=password This is wrong. So we need to change the transmitted data into the json format of {username:username,passsword:password} to avoid problems!

The sample code is as follows:

Copy code The code is as follows:
$(".submit").bind('click',function(){
var username = $("input[name='username']").val();
$.ajax({
url:"post",
type:"post",
dataType:"json",
data:"username="+username+"&password="+password,
timeout:5000,
error:function(){
alert(1)
},
success:function(){
}
})
})

Supplement: Four common ways to submit data via POST

① application/x-www-form-urlencoded

This should be the most common way to submit data via POST. For the browser's native form, if the enctype attribute is not set, data will eventually be submitted in application/x-www-form-urlencoded mode. The request is similar to the following (irrelevant request headers are omitted in this article):

Copy code The code is as follows:
POST http://www.bkjia.com HTTP/1.1
Content-Type: application/x-www-form-urlencoded;charset=utf-8

title=test&sub%5B%5D=1&sub%5B%5D=2&sub%5B%5D=3

First, the Content-Type is specified as application/x-www-form-urlencoded; secondly, the submitted data is encoded according to key1=val1&key2=val2, and both key and val are URL transcoded. Most server-side languages ​​have good support for this method. For example, in PHP, $_POST['title'] can get the value of title, and $_POST['sub'] can get the sub array.

Many times, we also use this method when submitting data using Ajax. For example, the Ajax of JQuery and QWrap, the default value of Content-Type is "application/x-www-form-urlencoded;charset=utf-8".

② multipart/form-data

This is another common way to submit POST data. When we use a form to upload files, the enctyped of the form must be equal to this value. Let’s look directly at an example request:

Copy code The code is as follows:
POST http://www.bkjia.com HTTP/1.1
Content-Type:multipart/form-data; boundary=----WebKitFormBoundaryrGKCBY7qhFd3TrwA

------WebKitFormBoundaryrGKCBY7qhFd3TrwA
Content-Disposition: form-data; name="text"

title
------WebKitFormBoundaryrGKCBY7qhFd3TrwA
Content-Disposition: form-data; name="file"; filename="chrome.png"
Content-Type: image/png

PNG ... content of chrome.png ...
------WebKitFormBoundaryrGKCBY7qhFd3TrwA--

This example is a little more complicated. First, a boundary is generated to separate different fields. In order to avoid duplication with the text content, the boundary is very long and complicated. Then Content-Type specifies that the data is encoded with mutipart/form-data, and what is the boundary content of this request. The message body is divided into multiple parts with similar structure according to the number of fields. Each part starts with --boundary, followed by content description information, followed by carriage return, and finally the specific content of the field (text or binary). If a file is being transferred, the file name and file type information must also be included. The message body ends with the --boundary-- flag. For a detailed definition of mutipart/form-data, please go to rfc1867.

This method is generally used to upload files, and major server languages ​​also have good support for it.
The two methods of POST data mentioned above are natively supported by browsers, and at this stage, native forms only support these two methods. But as more and more Web sites, especially WebApps, all use Ajax for data interaction, we can completely define new data submission methods to bring more convenience to development.

③ application/json

The Content-Type of application/json is certainly familiar to everyone as a response header. In fact, more and more people now use it as a request header to tell the server that the message body is a serialized JSON string. Due to the popularity of the JSON specification, all major browsers except lower versions of IE natively support JSON.stringify. Server-side languages ​​also have functions for processing JSON, so you will not encounter any trouble when using JSON.

It’s also useful that the JSON format supports much more complex structured data than just key-value pairs. I remember that when I was working on a project a few years ago, the data that needed to be submitted had a very deep level. I serialized the data into JSON and submitted it. But at that time, I used the JSON string as val, still placed it in the key-value pair, and submitted it in x-www-form-urlencoded mode.

The Ajax function in Google's AngularJS submits a JSON string by default. For example, the following code:

Copy code The code is as follows:
var data = {'title':'test', 'sub' : [1,2, 3]};
$http.post(url, data).success(function(result) {
...
});

The final request sent is:
Copy code The code is as follows:
POST http://www.bkjia.com HTTP/1.1
Content-Type: application/json;charset=utf-8

{"title":"test","sub":[1,2,3]}

This solution can easily submit complex structured data and is especially suitable for RESTful interfaces. Major packet capture tools, such as Chrome's own developer tools, Firebug, and Fiddler, will display JSON data in a tree structure, which is very friendly. However, some server-side languages ​​do not yet support this method. For example, php cannot obtain content from the above request through the $_POST object. At this time, you need to handle it yourself: when the Content-Type in the request header is application/json, obtain the original input stream from php://input, and then json_decode it into an object. Some PHP frameworks have already started doing this.

Of course AngularJS can also be configured to use x-www-form-urlencoded to submit data.

④ text/xml

XML-RPC (XML Remote Procedure Call) was mentioned before. It is a remote call specification that uses HTTP as the transport protocol and XML as the encoding method. A typical XML-RPC request looks like this:

Copy code The code is as follows:
POST http://www.bkjia.com HTTP/1.1
Content-Type: text/xml



examples.getStateName


41



The XML-RPC protocol is simple, functional and available in various languages. It is also widely used, such as WordPress's XML-RPC Api, seo/seo.html" target="_blank">search engine's ping service, etc. In JavaScript, there are also ready-made libraries that support data processing in this way. Interaction can well support existing XML-RPC services. However, I personally feel that the XML structure is still too bloated, and JSON will be more flexible and convenient in general scenarios

I hope this article will be helpful to everyone’s PHP programming design.

www.bkjia.comtruehttp: //www.bkjia.com/PHPjc/909351.htmlTechArticleA summary of common methods of php using ajax data to submit posts and posts, ajaxpost This article tells an example of php using ajax data to submit posts and post common methods. Share it with everyone for your reference. Specific methods...
Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn