The difference between Jquery AJAX POST and GET
1: The browser considers the GET access to be idempotent
that is, there is only one result for the same URL [the same means that the entire URL string matches exactly]
So if the URL string does not change during the second visit, the browser will directly After taking out the result of the first visit
POST is considered to be a changing access (the browser thinks that the submission of POST must have changed)
To prevent the idempotent access of GET, just add it after the URL? +new Date();, [In short, it makes the URL string different for each visit]
You should also abide by this principle when designing WEB pages
2: 1. Talk about the difference between Ajax Get and Post
Get method:
The get method can be used to transmit simple data, but the size is generally limited to 1KB. The data is appended to the URL and sent (HTTP header transmission). That is to say, the browser converts each form field element and its data according to the URL parameters. The format of is appended to the resource path in the request line. The most important point is that it will be cached by the client's browser, so others can read the customer's data, such as account number and password, etc. from the browser's history. Therefore, in some cases, the get method can cause serious security issues.
Post method:
When using the POST method, the browser sends each form field element and its data to the web server as the entity content of the HTTP message, instead of passing it as a parameter of the URL address. The amount of data transferred using the POST method The amount of data transmitted using the GET method is much larger.
In short, the GET method transmits a small amount of data, high processing efficiency, low security, and will be cached, while the opposite is true for POST.
Things to note when using the get method:
1 For get requests (or any involving url passing parameters), the passed parameters must first be processed by the encodeURIComponent method. Example: var url = "update.php?username=" + encodeURIComponent(username) + "&content=" +encodeURIComponent
(content)+"&id=1" ;
Please note when using the Post method:
1. Set the Context-Type of the header to application/x-www-form- urlencode ensures that the server knows that there are parameter variables in the entity. Typically SetRequestHeader("Context-Type","application/x-www-form-urlencoded;") of the XmlHttpRequest object is used. Example:
xmlHttp.setRequestHeader("Content-Type","application/x-www-form-urlencoded");
2. The parameters are key-value pairs with one-to-one name/value correspondence, and each pair of values is separated by an ampersand. Open. For example, var name=abc&sex=man&age=18, pay attention to the writing of var name=update.php?
abc&sex=man&age=18 and var name=?abc&sex=man&age=18;
3. The parameters are in Send Send in the (parameter) method, for example: xmlHttp.send(name); If it is the get method, directly xmlHttp.send(null);
4. Server-side request parameters distinguish Get and Post. If it is the get method, then $username = $_GET["username"]; If it is the post method, then $username = $_POST["username"];
AJAX garbled problem
Causes for garbled code:
1, xtmlhttp Return The default character encoding of the data is utf-8. If the client page is gb2312 or other encoded data, garbled characters will be generated. 2. The default character encoding of the data submitted by the post method is utf-8. If the server page is gb2312 or other encoded data Garbled characters will be generated
The solutions are:
1. If the client is gb2312 encoded, specify the output stream encoding on the server
2. Both the server and the client use UTF-8 encoding
gb2312:header('Content-Type :text/html;charset=GB2312');
utf8:header('Content-Type:text/html;charset=utf-8');
Note: If you have already followed the above method, still return If the code is garbled, check whether your method is get. For get requests (or any parameters passed by URL), the passed parameters must be processed by the encodeURIComponent method first. If encodeURIComponent is not used, garbled code will also be generated.

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Title: Methods and code examples to resolve 403 errors in jQuery AJAX requests. The 403 error refers to a request that the server prohibits access to a resource. This error usually occurs because the request lacks permissions or is rejected by the server. When making jQueryAJAX requests, you sometimes encounter this situation. This article will introduce how to solve this problem and provide code examples. Solution: Check permissions: First ensure that the requested URL address is correct and verify that you have sufficient permissions to access the resource.

jQuery is a popular JavaScript library used to simplify client-side development. AJAX is a technology that sends asynchronous requests and interacts with the server without reloading the entire web page. However, when using jQuery to make AJAX requests, you sometimes encounter 403 errors. 403 errors are usually server-denied access errors, possibly due to security policy or permission issues. In this article, we will discuss how to resolve jQueryAJAX request encountering 403 error

Build an autocomplete suggestion engine using PHP and Ajax: Server-side script: handles Ajax requests and returns suggestions (autocomplete.php). Client script: Send Ajax request and display suggestions (autocomplete.js). Practical case: Include script in HTML page and specify search-input element identifier.

How to solve the problem of jQueryAJAX error 403? When developing web applications, jQuery is often used to send asynchronous requests. However, sometimes you may encounter error code 403 when using jQueryAJAX, indicating that access is forbidden by the server. This is usually caused by server-side security settings, but there are ways to work around it. This article will introduce how to solve the problem of jQueryAJAX error 403 and provide specific code examples. 1. to make

Using Ajax to obtain variables from PHP methods is a common scenario in web development. Through Ajax, the page can be dynamically obtained without refreshing the data. In this article, we will introduce how to use Ajax to get variables from PHP methods, and provide specific code examples. First, we need to write a PHP file to handle the Ajax request and return the required variables. Here is sample code for a simple PHP file getData.php:

Ajax (Asynchronous JavaScript and XML) allows adding dynamic content without reloading the page. Using PHP and Ajax, you can dynamically load a product list: HTML creates a page with a container element, and the Ajax request adds the data to that element after loading it. JavaScript uses Ajax to send a request to the server through XMLHttpRequest to obtain product data in JSON format from the server. PHP uses MySQL to query product data from the database and encode it into JSON format. JavaScript parses the JSON data and displays it in the page container. Clicking the button triggers an Ajax request to load the product list.

Ajax is not a specific version, but a technology that uses a collection of technologies to asynchronously load and update web page content. Ajax does not have a specific version number, but there are some variations or extensions of ajax: 1. jQuery AJAX; 2. Axios; 3. Fetch API; 4. JSONP; 5. XMLHttpRequest Level 2; 6. WebSockets; 7. Server-Sent Events; 8, GraphQL, etc.

In order to improve Ajax security, there are several methods: CSRF protection: generate a token and send it to the client, add it to the server side in the request for verification. XSS protection: Use htmlspecialchars() to filter input to prevent malicious script injection. Content-Security-Policy header: Restrict the loading of malicious resources and specify the sources from which scripts and style sheets are allowed to be loaded. Validate server-side input: Validate input received from Ajax requests to prevent attackers from exploiting input vulnerabilities. Use secure Ajax libraries: Take advantage of automatic CSRF protection modules provided by libraries such as jQuery.
