Skip to content
September 10, 2026
  • Bluesky
  • Facebook
  • Linkedin
  • Mastodon
  • RSS
  • Twitter
  • Youtube

Daily CyberSecurity

Zero-hour alerts. Unmatched analysis.

Primary Menu
  • Home
  • CVE Data
    • CVE Watchtower
    • Top Exploited CVEs
    • CVE Stats by Vendor
    • Q2 2026 Report
    • CVE Alerts
    • CVE Alert Settings
    • Pricing
  • Cyber Criminals
  • Data Leak
  • Linux
  • Malware
  • Vulnerability
  • Submit Press Release
  • Weekly Recap
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
Share on FacebookShare on XShare on LinkedInShare on TelegramShare on BlueskyShare on Mastodon
Tags: Ajax GET post

Search

Translation

CVE ALERTS
📧

Email Delivery
Get threat intel straight to your inbox.

♾️

Unlimited Vendors
Track every technology in your stack.

🚨

All New CVE Alerts
Be the first to know about new flaws.

⚙️

Custom EPSS Threshold
Filter noise, focus on real risks.

💬

Slack & Teams Webhook
Integrate directly into your SecOps.

🚫

100% Ad-Free
Enjoy an uninterrupted reading experience.

$7/mo
Subscribe Now

🚨 Active Exploits in the Wild

  • CVE-2026-20079CVSS 10.0
    A vulnerability in the web interface of Cisco Secure Firewall Management Center (FMC) Software could allow an unauthenticated,...
    Admin intelCISA KEV📅 Added to KEV: Sep 9, 2026📅 Updated: Sep 9, 2026
  • CVE-2025-25249CVSS 8.1
    A heap-based buffer overflow vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiOS 7.4.0 through 7.4.8, FortiOS 7.2.0 through...
    Admin intelCISA KEV📅 Added to KEV: Sep 9, 2026📅 Updated: Sep 9, 2026
  • CVE-2026-87491
    Out of bounds write in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute...
    Admin intelCISA KEV📅 Added to KEV: Sep 9, 2026📅 Updated: Sep 9, 2026
  • CVE-2026-19490
    Vulnerability in NetScaler ADC and NetScaler Gateway. This issue affects ADC: from 14.1 through 73.32 and from 13.1...
    CISA KEV📅 Added to KEV: Sep 9, 2026
  • CVE-2026-75650CVSS 10.0
    Adobe Commerce is affected by an Improper Neutralization of Special Elements Used in a Template Engine vulnerability that...
    Admin intelCISA KEV📅 Added to KEV: Sep 8, 2026📅 Updated: Sep 8, 2026
  • CVE-2026-81963CVSS 7.8
    Improper link resolution before file access ('link following') in Windows Update Stack allows an authorized attacker to elevate...
    CISA KEV📅 Added to KEV: Sep 8, 2026
  • CVE-2026-85880CVSS 7.8
    Heap-based buffer overflow in Windows ALPC allows an authorized attacker to elevate privileges locally.
    CISA KEV📅 Added to KEV: Sep 8, 2026
  • CVE-2026-86218CVSS 10.0
    N-central is vulnerable to a pre-auth remote code execution This issue affects N-central: before 2026.3.1.14.
    Admin intelCISA KEV📅 Added to KEV: Sep 8, 2026📅 Updated: Sep 7, 2026
Powered by CVE Watchtower

🔴 Live Critical Threats

  • CVE-2026-9163CVSS 9.8
    Improper neutralization of special elements used in an SQL command ('SQL injection')...
  • CVE-2026-8323CVSS 9.3
    URL redirection to untrusted site ('open redirect') vulnerability in Armiya Information Technologies...
  • CVE-2026-88285CVSS 9.4
    GeoVision GV-LPC2211 V1.13 exposes a network-accessible PTZ control service without authentication, allowing...
  • CVE-2026-88278CVSS 9.8
    GeoVision GV-LPC2211 V1.13 fails to enforce WS-Security UsernameToken freshness or nonce reuse...
  • CVE-2026-44950CVSS 9.0
    fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) copies each glyph's bitmap into...
  • CVE-2026-7188CVSS 9.8
    Improper neutralization of special elements used in an SQL command ('SQL injection')...
  • CVE-2026-59679CVSS 9.0
    fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) indexes the per-character encoding[] array...
  • CVE-2026-19583CVSS 9.9
    Velociraptor allows some sensitive artifacts to be gated by additional permissions. For...
  • CVE-2026-18351CVSS 9.8
    The Drag and Drop File Upload for Elementor Forms plugin for WordPress...
  • CVE-2026-87931CVSS 9.6
    A vulnerability has been found in Behavioral Technology Group Pavlok Behavioral Conditioning...
Powered by CVE WATCHTOWER

Our Websites
  • Penetration Testing Tools
  • The Daily Information Technology
  • Top Exploited CVEs
  • Daily CyberSecurity

    • About SecurityOnline.info
    • Advertise with us
    • Announcement
    • Contact
    • Contributor Register
    • Login
    • Disclaimer
    • DCMA
    • Privacy Policy
    • 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

    • CVE Watchtower
    • CVE Statistics by Vendor 2026
    • Q2 2026 Report
    • Top Exploited CVEs
    • Bluesky
    • Facebook
    • Linkedin
    • Mastodon
    • RSS
    • Twitter
    • Youtube
    © 2017 - 2026 Daily CyberSecurity. All Rights Reserved.