blocks|key|1379172|text|我建议显式地使用$_POST和$_GET。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1379173|通过适当的网站设计，使用$_REQUEST应该是不必要的，而且它也有一些缺点，比如让你更容易受到CSRF/XSS攻击，以及在网址中存储数据的其他愚蠢行为。|1379174|无论哪种方式，速度差异都应该是最小的。|1379175|entityMap^0|8|6|F|5|0|1C|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

I'd suggest using <code>$_POST</code> and <code>$_GET</code> explicitly. 

Using $_REQUEST should be unnecessary with proper site design anyway, and it comes with some downsides like leaving you open to easier <code>CSRF/XSS</code> attacks and other silliness that comes from storing data in the URL.

The speed difference should be minimal either way.

blocks|key|1379076|text|使用请求。没有人关心这样一个简单操作的速度，而且它的代码要干净得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1379077|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Use REQUEST. Nobody cares about the speed of such a simple operation, and it's much cleaner code.

blocks|key|1379311|text|if+(isset($_GET['s']))+{
++$temp+=+$_GET['s'];
}
else+{
++$temp+=+$_POST['s'];
}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1379312|使用它是因为它更安全，而且不会产生明显的速度差异|unstyled|1379313|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>if (isset($_GET['s'])) {
 $temp = $_GET['s'];
}
else {
 $temp = $_POST['s'];
}
</code></pre>

Use that because it is safer and it won't make noticeable speed difference

blocks|key|1379435|text|$_GET从查询字符串或URL.>中检索变量|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1379436|$_POST从POST方法检索变量，例如(通常)表单。|1379437|$_REQUEST是$_GET和$_POST的合并，其中$_POST覆盖了$_GET。在自引用表单上使用$_REQUEST进行验证是很好的。|1379438|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

$_GET retrieves variables from the querystring, or your URL.>

$_POST retrieves variables from a POST method, such as (generally) forms.

$_REQUEST is a merging of $_GET and $_POST where $_POST overrides $_GET. Good to use $_REQUEST on self refrential forms for validations.

blocks|key|1164128|text|我会使用第二种方法，因为它更明确。否则你就不知道变量是从哪里来的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164129|为什么你需要同时检查GET和POST？当然，使用其中之一只会更有意义。|1164130|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I would use the second method as it is more explicit. Otherwise you don't know where the variables are coming from.

Why do you need to check both GET and POST anyway? Surely using one or the other only makes more sense.

blocks|key|1379285|text|我只使用过_GET或_POST。我更喜欢有控制权。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1379286|我不喜欢OP中的两个代码片段的一个地方是，它们丢弃了使用哪个HTTP方法的信息。这些信息对于输入过滤很重要。|1379287|例如，如果脚本接受来自将要输入到DB中的表单的数据，那么该表单最好使用POST+(use+GET+only+for+idempotent+actions)。但是，如果脚本通过GET方法接收输入数据，那么它(通常)应该被拒绝。对我来说，这种情况可能需要在错误日志中写入安全违规，因为这是某人正在尝试某些东西的迹象。|offset|length|1379288|对于OP中的任何一段代码，这种清理都是不可能的。|1379289|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html^0|0|0|15|Z|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I only ever use _GET or _POST. I prefer to have control.

What I don't like about either code fragment in the OP is that they discard the information on which HTTP method was used. And that information is important for input sanitization.

For example, if a script accepts data from a form that's going to be entered into the DB then the form had better use POST (<a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html" rel="nofollow noreferrer">use GET only for idempotent actions</a>). But if the script receives the input data via the GET method then it should (normally) be rejected. For me, such a situation might warrant writing a security violation to the error log since it's a sign somebody is trying something on.

With either code fragment in the OP, this sanitization wouldn't be possible.

blocks|key|1379369|text|我会使用$_POST和$_GET，因为与$_REQUEST不同，它们的内容不受variables_order的影响。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1379370|何时使用$_POST和$_GET取决于正在执行的操作类型。更改从服务器处理的数据的操作应通过POST请求完成，而其他操作应通过GET请求完成。举个例子，删除用户账号的操作不应该在用户点击链接后直接执行，而可以通过链接查看图像。|1379371|entityMap^0|4|6|B|5|K|9|13|F|0|4|6|B|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|I|$]]

I would use <code>$_POST</code>, and <code>$_GET</code> because differently from <code>$_REQUEST</code> their content is not influenced by <code>variables_order</code>. 
When to use <code>$_POST</code> and <code>$_GET</code> depends on what kind of operation is being executed. An operation that changes the data handled from the server should be done through a POST request, while the other operations should be done through a GET request. To make an example, an operation that deletes a user account should not be directly executed after the user click on a link, while viewing an image can be done through a link.

blocks|key|1164467|text|我用这个，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164468|$request+=+(count($_REQUEST)+>+1)?$_REQUEST:$_GET;|code-block|syntax|javascript|1164469|这条语句验证$_REQUEST是否有多个参数(+$_REQUEST中的第一个参数是请求uri，可以在需要的时候使用)，一些PHP包不会返回$_GET，所以检查$_GET的参数是否大于1，默认情况下，它将是$_POST。|1164470|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I use this,

<pre><code>$request = (count($_REQUEST) &gt; 1)?$_REQUEST:$_GET;
</code></pre>

the statement validates if $_REQUEST has more than one parameter (the first parameter in $_REQUEST will be the request uri which can be used when needed, 
some PHP packages wont return $_GET so check if its more than 1 go for $_GET, By default, it will be $_POST.

blocks|key|1164206|text|你过早地进行了优化。此外，出于安全原因，您应该认真考虑是否应将GET用于发布的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164207|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You are prematurely optimizing. Also, you should really put some thought into whether GET should be used for stuff you're POST-ing, for security reasons.

blocks|key|1164577|text|它很难看，我不建议将它作为最终的解决方案，但在构建rest函数时，有时有一个‘通用’参数抓取器是很方便的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164578|public+static+function+parseParams()+{
++++$params+=+array();
++++switch($_SERVER['REQUEST_METHOD'])+{
++++++++case+"PUT":
++++++++case+"DELETE":
++++++++++++parse_str(file_get_contents('php://input'),+$params);
++++++++++++$GLOBALS["_{$_SERVER['REQUEST_METHOD']}"]+=+$params;
++++++++++++break;
++++++++case+"GET":
++++++++++++$params+=+$_GET;
++++++++++++break;
++++++++case+"POST":
++++++++++++$params+=+$_POST;
++++++++++++break;
++++++++default:
++++++++++++$params+=+$_REQUEST;
++++++++++++break;
++++}
++++return+$params;
}|code-block|syntax|javascript|1164579|一些有创造力的人甚至可以添加它来处理命令行参数或任何来自您的IDE的东西。一旦决定了给定的rest-function正在做什么，就可以为该给定的调用选择合适的rest-function，以确保获得部署版本所需的内容。这假设设置了'REQUEST_METHOD‘。|1164580|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

It's ugly and I wouldn't recommended it as a final solution when pushing code live, but while building rest functions, it's sometimes handy to have a 'catch-all' parameter grabber:

<pre><code>public static function parseParams() {
 $params = array();
 switch($_SERVER['REQUEST_METHOD']) {
 case "PUT":
 case "DELETE":
 parse_str(file_get_contents('php://input'), $params);
 $GLOBALS["_{$_SERVER['REQUEST_METHOD']}"] = $params;
 break;
 case "GET":
 $params = $_GET;
 break;
 case "POST":
 $params = $_POST;
 break;
 default:
 $params = $_REQUEST;
 break;
 }
 return $params;
}
</code></pre>

Someone creative could probably even add to it to handle command line parameters or whatever comes from your IDE. Once you decide what a given rest-function is doing, you can pick one appropriate for that given call to make sure you get what you need for the deploy version.
This assumes 'REQUEST_METHOD' is set.

Which of these code will be faster?

<pre><code>$temp = $_REQUEST['s'];
</code></pre>

or

<pre><code>if (isset($_GET['s'])) {
 $temp = $_GET['s'];
}
else {
 $temp = $_POST['s'];
}
</code></pre>

Among $_REQUEST, $_GET and $_POST which one is the fastest?

33 天实现自己的 AI 进化论？发文瓜分机械键盘、耳机等万元奖池！点击参加活动：<a href="https://cloud.tencent.com/developer/article/2503022" target="_blank">https://cloud.tencent.com/developer/article/2503022</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/01543e0407db10898a7ee9f420794432.jpg"/>

技术创作特训营有奖征文

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

文章&问答评论现已支持表情

这些代码中哪一个会更快？$temp = $_REQUEST['s'];或if (isset($_GET['s'])) {  $temp = $_GET['s'];}else {  $temp = $_POST['s'];}

问在$_REQUEST、$_GET和$_POST中，哪一个最快？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在$_REQUEST、$_GET和$_POST中，哪一个最快？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在$_REQUEST、$_GET和$_POST中，哪一个最快？
EN