GET vs POST: Uncover the Real Differences Behind HTTP Requests
This article explains the fundamental distinctions between GET and POST HTTP methods, covering how parameters are transmitted, browser and server constraints, underlying TCP behavior, and why POST often requires two TCP packets while GET typically uses only one.
GET and POST are the two basic HTTP request methods that every web developer should understand.
The most common "standard answer" lists differences such as:
GET parameters appear in the URL and are safe for browser back‑navigation; POST parameters are sent in the request body and may be resubmitted.
GET URLs can be bookmarked; POST requests cannot.
Browsers cache GET requests automatically, while POST requests are not cached unless explicitly configured.
GET supports only URL‑encoded data; POST supports multiple encoding types.
GET parameters remain in browser history; POST parameters do not.
GET URLs have length limits (typically ~2 KB in browsers, ~64 KB on servers); POST has no practical length limit.
GET accepts only ASCII characters; POST has no character restrictions.
GET exposes parameters in the URL, making it less secure for sensitive data.
GET sends parameters via URL, POST places them in the request body.
Both methods operate over TCP/IP, so at the transport layer they are essentially the same TCP connection.
HTTP defines how parameters are transmitted: GET places data in the URL, while POST places data in the request body. However, browsers and servers impose practical limits—most browsers restrict URL length to about 2 KB, and many servers reject URLs larger than 64 KB.
When using GET, the client can technically include a request body, but server handling of such bodies is inconsistent.
In terms of packet flow, a GET request typically sends a single TCP packet containing both headers and data, receiving a single 200 OK response. A POST request usually involves two packets: the client sends headers, the server replies with a 100 Continue, then the client sends the body, and finally the server returns a 200 OK response. This extra round‑trip makes POST slightly slower, which is why some performance guides suggest using GET when appropriate.
Despite these differences, the semantics of GET (safe, idempotent) and POST (non‑idempotent) should guide their proper use.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Programmer DD
A tinkering programmer and author of "Spring Cloud Microservices in Action"
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.