• About WordPress
    • WordPress.org
    • Documentation
    • Learn WordPress
    • Support
    • Feedback
Skip to content
May 25, 2026
  • Linkedin
  • Twitter
  • Facebook
  • Youtube

Daily CyberSecurity

Zero-hour alerts. Unmatched analysis.

Primary Menu
  • Home
  • CVE Watchtower
  • Cyber Criminals
  • Data Leak
  • Linux
  • Malware
  • Vulnerability
  • Submit Press Release
  • Vulnerability Report
Light/Dark Button
  • Home
  • Technique
  • The difference between POST & GET in Ajax
  • Technique

The difference between POST & GET in Ajax

Ddos September 8, 2017 3 minutes read
ajax

Get and Post are sent to the server a request, but the sending mechanism is different.

1. GET request will be passed in the parameter with the URL , while the POST request is sent as an entity of the content of the HTTP message to the WEB server. Of course, in the Ajax request, this distinction is not visible to the user.

2. The first is “GET method to submit the data can only be up to 1024 bytes”, because GET is submitted through the URL data, then GET can submit the amount of data just like the length of the URL has a direct relationship. In fact, the URL does not exist the upper limit of the problem, HTTP protocol specification does not limit the length of the URL. This restriction is limited by the specific browser and the server. IE limits the length of the URL to 2083 bytes (2K + 35). For other browsers, such as Netscape, FireFox, etc., there is no length limit in theory, and its limitations depend on the support of the operating system. Note that this is the length of the entire URL length, not just your parameter value data length .

3. GET method The requested data is cached by the browser , so others can read the data from the browser’s history, such as account numbers and passwords. In some cases, the GET approach can cause serious security problems . The POST method is relatively easy to avoid these problems.

get the difference between the request and the post request on the server side :

4. When the client uses the get request, the server uses Request.QueryString to get the parameters, and the client uses the post request, the server uses the Request.Form to get the parameters.

The HTTP standard contains these two methods for a different purpose. POST is used to create resources, the contents of the resource will be included in the contents of the HTTP request. For example, to process an order form, add new rows to the database, and so on. When the request for no side effects (such as search), you can use the GET method; when the request for side effects (such as adding data lines), then use the POST method . A more practical question is that the GET method may produce a long URL that may exceed the limits of the URL length of some browsers and servers.

If any of the following conditions are met, the GET method is used:

  • The request is to find the resource, and the HTML form data is only used to help the search.
  • Request results without persistent side effects.
  • The total length of the collected data and the input field name within the HTML form does not exceed 1024 characters.

If any of the following conditions are met, the POST method is used:

  • The result of the request has a persistent side effect, for example, adding a new row of data in the database.
  • If you use the GET method, the data collected on the form may make the URL too long.
  • The data to be transmitted is not a 7-bit ASCII code.

 

Share this article:

Facebook Post LinkedIn Telegram

No related posts.

Tags: Ajax GET post

Search

Translation

CVE WATCHTOWER
🚨

Receive alerts for vulnerabilities being exploited in the wild.

⚑

Get notified instantly when a Proof of Concept (PoC) exploit is published.

πŸ”

Access critical info on vulnerabilities even when marked as "RESERVED".

🧠

Insights powered by decades of expertise and global intelligence sources.

🎯

Customize alerts with up to 10 keywords for your specific tech stack.

πŸ“Š

Export the raw CVE database for SIEM integration and reporting.

Upgrade Package

πŸ”΄ Live Critical Threats

  • CVE-2026-9458CVSS 9.8
    A vulnerability was identified in Totolink A8000RU 7.1cu.643_b20200521. The impacted element is...
  • CVE-2026-9457CVSS 9.8
    A vulnerability was determined in Totolink A8000RU 7.1cu.643_b20200521. The affected element is...
  • CVE-2026-9456CVSS 9.8
    A vulnerability was found in Totolink A8000RU 7.1cu.643_b20200521. Impacted is the function...
  • CVE-2026-9455CVSS 9.8
    A vulnerability has been found in Totolink A8000RU 7.1cu.643_b20200521. This issue affects...
  • CVE-2026-9454CVSS 9.8
    A flaw has been found in Totolink A8000RU 7.1cu.643_b20200521. This vulnerability affects...
  • CVE-2026-9436CVSS 9.8
    A flaw has been found in Totolink A8000RU 7.1cu.643_b20200521. The impacted element...
  • CVE-2026-9435CVSS 9.8
    A vulnerability was detected in Totolink A8000RU 7.1cu.643_b20200521. The affected element is...
  • CVE-2026-9434CVSS 9.8
    A security vulnerability has been detected in Totolink A8000RU 7.1cu.643_b20200521. Impacted is...
  • CVE-2026-9433CVSS 9.8
    A weakness has been identified in Totolink A8000RU 7.1cu.643_b20200521. This issue affects...
  • CVE-2026-2651CVSS 9.0
    A vulnerability in MLflow versions
Powered by CVE WATCHTOWER

Recent Zero-Day Vulnerabilities

  • Exploited in the Wild: Critical OWA Spoofing Flaw (CVE-2026-42897) Hits On-Premises Exchange Servers
  • Exploited in the Wild: Maximum CVSS 10 SD-WAN Flaw (CVE-2026-20182) Grants Admin Control
  • Exploited in the Wild: Critical 9.8 CVSS RCE Hits Canon GUARDIANWALL MailSuite
  • Exploit Code Released: Public PoC Dumps for Windows BitLocker Bypass and SYSTEM Elevation Zero-Days
  • Exploited in the Wild: “Dirty Frag” Linux Vulnerability Grants Instant Root Access
  • Under Active Attack: Ivanti EPMM Zero-Day Exploited in the Wild via Harvested Admin Credentials
Our Websites
  • Penetration Testing Tools
  • The Daily Information Technology
  • Daily CyberSecurity

    • About SecurityOnline.info
    • Advertise with us
    • Announcement
    • Contact
    • Contributor Register
    • Login
    • About SecurityOnline.info
    • Advertise on SecurityOnline.info
    • Contact Us

    When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works

    • Disclaimer
    • Privacy Policy
    • DMCA NOTICE
    • Linkedin
    • Twitter
    • Facebook
    • Youtube
    Copyright Daily CyberSecurity Β© All rights reserved.