Skip to content
June 22, 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

Do Son 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
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-5366CVSS 9.9
    Prefect version 3.6.23 is vulnerable to remote code execution due to improper...
  • CVE-2024-58351CVSS 9.8
    Flowise before 2.1.4 allows configuration to be injected into the Chainflow during...
  • CVE-2022-50972CVSS 9.8
    WooCommerce 7.1.0 contains a remote code execution vulnerability that allows attackers to...
  • CVE-2019-25763CVSS 9.8
    WordPress Ultimate Addons for Beaver Builder 1.2.4.1 contains an authentication bypass vulnerability...
  • CVE-2026-11551CVSS 9.8
    The Branda plugin for WordPress is vulnerable to privilege escalation via account...
  • CVE-2026-56081CVSS 9.1
    Cap-go before 12.128.2 contains an authentication logic flaw that lets an attacker...
  • CVE-2026-56073CVSS 9.4
    Cap-go before 12.128.2 contains an authentication bypass vulnerability in OTP verification that...
  • CVE-2026-55447CVSS 9.6
    ### Summary All components based on `BaseFileComponent` are vulnerable to the following...
  • CVE-2026-48584CVSS 9.9
    Execution with unnecessary privileges in Azure Synapse allows an authorized attacker to...
  • CVE-2026-48582CVSS 9.6
    Missing authorization in Microsoft Exchange Online allows an authorized attacker to elevate...
Powered by CVE WATCHTOWER

Recent Zero-Day Vulnerabilities

  • GreatXML BitLocker Bypass: Public PoC Exploit Disclosed
  • Check Point VPN Vulnerability Exploited in the Wild with Ransomware Links
  • Weekly Threat Intelligence: June 1 to June 7, 2026
  • Cisco SD-WAN Vulnerability Exploited in the Wild with Root RCE Risks
  • Android Zero-Day Flaw Exploited in the Wild: June 2026 Patches Released
  • Exploited in the Wild: Critical OWA Spoofing Flaw (CVE-2026-42897) Hits On-Premises Exchange Servers
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
    © 2017 - 2026 Daily CyberSecurity. All Rights Reserved.