当前位置：文江博客话题详情

POST 与 GET 方法 - 在网络级别，哪个受延迟影响更大？

发布于 2024-09-26 08:51:52 字数 166 浏览 4 评论 0原文

HTTP GET 和 POST 请求的网络通信有什么区别吗？

使用 GET，我知道整个请求是一次性发送的。使用 POST，我认为发送了初始请求，然后发送了第二个请求，该请求发送了所有参数。

例如，假设服务器和客户端之间的延迟为 500ms。 GET 与 POST 调用的总时间是多少？

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

天邊彩虹 2024-10-03 08:51:52

报文均为TCP报文，承载HTTP协议，请求方式不会改变网络层的响应时间。

它会根据请求的大小而根据请求的大小而变化，但这不是由请求类型决定的。

您可以通过 post 发送比 get 更多的数据，但这并不意味着它们响应速度更快，这是一个单独的问题。

HTTP 服务器处理和返回结果的速度取决于您正在使用的服务器，并且可能非常微不足道，不值得一提。

从服务器返回结果的速度取决于HTTP服务器正在处理什么资源，如果它调用需要时间的PHP文件，那么它将需要时间......

数据包没有明显的区别...这是通过 SSL 的 GET 请求：

00907f8252f7001e4fe86a93080045000028
0bb2400080067380ac100167adc22064c51a
01bb66ccad148448d84850103f05bde90000

这是通过 SSL 的 POST 请求：

00907f8252f7001e4fe86a93080045000028
0c0640008006732cac100167adc22064c511
01bbe538c0df8621dc6150104042248c0000

对于 TCP 数据包内的字符串是“GET”还是“POST”，网络会查看，并没有太多涉及它说：“哦，你是 TCP，嗯？好吧，那你就走吧。”它不在乎。

正常网络流量之外的任何延迟都完全是由于服务器级别的处理或其正在运行的代码造成的。

The packets are all TCP packets, which carry the HTTP protocol, the request method doesn't change the network layer's response time.

It will change on request-to-request basis depending on the size of a request, but that's not determined by the request type.

You can send more data with post than get, but this doesn't mean they respond faster, it's a separate issue.

The speed at which the HTTP server can process and return a result is on the server you're using, and likely to be so negligible it's not worth mentioning.

The speed at which the result comes back from the server depends on what resource the HTTP server is processing, if it's calling a PHP file that takes time, then it's going to take time...

There isn't a clear difference in the packets... this is a GET request over SSL:

00907f8252f7001e4fe86a93080045000028
0bb2400080067380ac100167adc22064c51a
01bb66ccad148448d84850103f05bde90000

And this is a POST request over SSL:

00907f8252f7001e4fe86a93080045000028
0c0640008006732cac100167adc22064c511
01bbe538c0df8621dc6150104042248c0000

There isn't exactly a lot of involvement of whether the string inside the TCP packet is "GET" or "POST," the network looks at it, says "oh, you're TCP, Huh? Well, off you go then." It doesn't care.

Any delay outside of normal network traffic is soley due to processing on the sever level, or on the code it's working through.

回复收藏 0 原文

爱要勇敢去追 2024-10-03 08:51:52

由于日志记录较少，POST 请求具有优势

给定相同数量的信息（POST 消息不超过 GET），POST 在技术上在服务器端应该更快（纳秒到皮秒）：

通常是 Web 服务器，例如 Apache，在某处记录请求
POST 请求不会记录查询字符串，因此会减少写入处理。服务器 IOPS 可能会无意中影响延迟
如果没有这个，给定相同的数据包，它们实际上是等效的。
GET 将数据存储在查询字符串中，POST 将信息存储在消息正文中。
服务器处理两者，只是以不同的方式。

在客户端，POST 需要更多处理来准备消息。如果执行任何 AJAX，您会注意到这一点，发送 GET 请求比 POST 容易得多。

GET 的性能优于 POST 请求

正如 w3 在 HTTP/1.1 上所定义的，GET有能力执行部分请求，从而限制网络带宽：
<块引用>
如果请求消息包含 Range 标头字段，则 GET 方法的语义将更改为“部分 GET”。部分 GET 请求仅传输实体的一部分，如第 14.35 节所述。部分 GET 方法旨在通过允许完成部分检索的实体而不传输客户端已持有的数据来减少不必要的网络使用。
此外，w3 描述了条件 GET 以减少网络使用：
<块引用>
如果请求消息包含 If-Modified-Since、If-Unmodified-Since、If-Match、If-None-Match 或 If-Range 标头字段，则 GET 方法的语义更改为“条件 GET” 。条件 GET 方法请求仅在条件标头字段描述的情况下传输实体。条件 GET 方法旨在通过允许刷新缓存实体而不需要多个请求或传输客户端已持有的数据来减少不必要的网络使用。
GET 请求是可缓存的。这会减少网络带宽，因为浏览器可能会看到过去已经发出的请求，该请求尚未过期，并通过来自缓存的看似即时的响应进行响应。

POST requests have edge due to less logging

Given the same amount of information (the POST message doesn't exceed the GET), POST should technically be faster on the serverside (by nano-to-picoseconds):

Generally web servers, like Apache, log the requests somewhere
POST requests do not log the query string, thus less write processing. Server IOPS may inadvertently affect latency
Without this, given the same packets, they're practically equivalent.
The GET stores data in the query string, the POST stores the info in the message body.
The server processes both, just in different ways.

On the client side, the POST requires more processing to prepare the message. You'll notice this if doing any AJAX, it's a lot easier to send a GET request than POST.

GET has the ability to outperform POST requests

As defined by w3 on HTTP/1.1, the GET has the ability to perform a partial request, thus limiting the network bandwidth:
The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial GET requests that only part of the entity be transferred, as described in section 14.35. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed without transferring data already held by the client.
Additionally, w3 describes a conditional GET to reduce network usage:
The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the entity be transferred only under the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce unnecessary network usage by allowing cached entities to be refreshed without requiring multiple requests or transferring data already held by the client.
GET requests are cacheable. This reduces network bandwidth because a browser may see a request that has already been made in the past, which isn't expired yet and responds by a seemingly instantaneous response from cache.

回复收藏 0 原文

沫离伤花 2024-10-03 08:51:52

我在 Wireshark 中进行监控时对此进行了测试。

我创建了一个简单的 HTML 表单，并在 GET 和 POST 之间切换方法。

我始终注意到 GET 请求发送一个数据包，而 POST 发送两个数据包。
即使表单数据非常小，POST 数据也始终在第二个数据包中发送。

这对我来说意味着 POST 会更容易受到延迟的影响。

更新 2011.07.05：

这是用于 POST 的简单 HTML 表单：

<form method="GET" action="/form-handler.aspx">
<input type="hidden" value="12345" />
<input type="submit" value="click to submit" />
</form>

这是 POST 版本：

<form method="POST" action="/form-handler.aspx">
<input type="hidden" value="12345" />
<input type="submit" value="click to submit" />
</form>

I tested this while monitoring in Wireshark.

I created a simple HTML form and toggled the method between GET and POST.

Consistently, I noticed that GET requests send one packet, while POST sends two.
Even when the form data is very small, the POST data is always sent in the second packet.

This suggests to me that POST would be more impacted by latency.

UPDATE 2011.07.05:

Here is the simple HTML form for POST:

<form method="GET" action="/form-handler.aspx">
<input type="hidden" value="12345" />
<input type="submit" value="click to submit" />
</form>

Here is the POST version:

<form method="POST" action="/form-handler.aspx">
<input type="hidden" value="12345" />
<input type="submit" value="click to submit" />
</form>

回复收藏 0 原文

十年不长 2024-10-03 08:51:52

对于给定的数据，它们可能非常接近相同。 GET 请求可能如下所示：

GET /test?x=5&y=3&z=4 HTTP/1.1
Header1: value
Header2: value
...

这是与 POST 请求相同的方式：

POST /test HTTP/1.1
Header1: value
Header2: value
...

x=5&y=3&z=4

因此，数据量相同。真正的问题是您是否希望用户能够添加书签并返回到 URL 并在将来再次看到相同的数据。 GET 用于此目的，POST 用于请求在服务器上更改数据，或者出于安全原因（例如，不要使用 GET 提交密码）。

For a given piece of data, they will likely be very nearly the same. Here is what a GET request may look like:

GET /test?x=5&y=3&z=4 HTTP/1.1
Header1: value
Header2: value
...

Here is how the same would look as a POST:

POST /test HTTP/1.1
Header1: value
Header2: value
...

x=5&y=3&z=4

So it's the same amount of data. The real question is whether you want the user to be able to bookmark and return to the URL and see the same data again in the future. GETs are used for that, POSTs are used for requesting data be changed on the server, or for security reasons (don't use GET to submit a password, for example).

回复收藏 0 原文