Skip to content

doc: updateSafeMethodsAndIdempotentMethods #42010

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Nov 19, 2025
+1 −1
Merged

doc: updateSafeMethodsAndIdempotentMethods #42010

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
d667cef
doc: updateSafeMethodsAndIdempotentMethods
Nov 19, 2025
e7cd2db
Update files/en-us/web/http/guides/connection_management_in_http_1.x/…
samuel871211 Nov 19, 2025
2123ccf
Remove TRACE method from safe HTTP methods list
samuel871211 Nov 19, 2025
26202d7
Fix formatting of safe HTTP methods explanation
samuel871211 Nov 19, 2025
9b74446
Update safe methods list in HTTP glossary
samuel871211 Nov 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion files/en-us/web/http/guides/connection_management_in_http_1.x/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ By default, [HTTP](/en-US/docs/Web/HTTP) requests are issued sequentially. The n

Pipelining is the process to send successive requests, over the same persistent connection, without waiting for the answer. This avoids latency of the connection. Theoretically, performance could also be improved if two HTTP requests were to be packed into the same TCP message. The typical [MSS](https://en.wikipedia.org/wiki/Maximum_segment_size) (Maximum Segment Size), is big enough to contain several simple requests, although the demand in size of HTTP requests continues to grow.

Not all types of HTTP requests can be pipelined: only {{Glossary("idempotent")}} methods, that is {{HTTPMethod("GET")}}, {{HTTPMethod("HEAD")}}, {{HTTPMethod("PUT")}} and {{HTTPMethod("DELETE")}}, can be replayed safely. Should a failure happen, the pipeline content can be repeated.
Not all types of HTTP requests can be pipelined: only {{Glossary("idempotent")}} methods, that is {{HTTPMethod("GET")}}, {{HTTPMethod("HEAD")}}, {{HTTPMethod("OPTIONS")}}, {{HTTPMethod("TRACE")}}, {{HTTPMethod("PUT")}}, and {{HTTPMethod("DELETE")}}, can be replayed safely. Should a failure happen, the pipeline content can be repeated.

Today, every HTTP/1.1-compliant proxy and server should support pipelining, though many have limitations in practice: a significant reason no modern browser activates this feature by default.

Expand Down