blocks|key|312087|text|你的第二个问题很简单，GET在服务器端和浏览器端都有1-2千字节的大小限制，所以任何类型的更大数量的数据都必须通过POST发送。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|312088|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|$]]

Your second question is easy, GET has a size limitation of 1-2 kilobytes on both the server and browser side, so any kind of larger amounts of data you'd have to send through POST.

blocks|key|3047072|text|通常的规则应该适用于发送请求的方式。如果请求是检索信息(例如，部分搜索“提示”结果，或要显示的新页面，等等)您可以使用GET。如果发送的数据是更改某些内容(更新数据库、删除记录等)请求的一部分。然后使用POST。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3047073|在服务器端，没有理由使用原始输入，除非您想一次性获取整个post/get数据块。您可以像往常一样通过_GET/_POST数组检索所需的特定信息。像MooTools/jQuery这样的AJAX库将为您处理实际的AJAX调用和将表单数据编码为适当格式的困难部分。|3047074|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|$]]

The usual rules should apply for how you send the request. If the request is to retrieve information (e.g. a partial search 'hint' result, or a new page to be displayed, etc...) you can use GET. If the data being sent is part of a request to change something (update a database, delete a record, etc..) then use POST.

Server-side, there's no reason to use the raw input, unless you want to grab the entire post/get data block in a single go. You can retrieve the specific information you want via the _GET/_POST arrays as usual. AJAX libraries such as MooTools/jQuery will handle the hard part of doing the actual AJAX calls and encoding form data into appropriate formats for you.

blocks|key|3260826|text|对于JSON数据，将其发布为"application/json“content-type要容易得多。如果使用GET，则必须在参数中对JSON进行URL编码，这有点麻烦。而且，当你发布的时候没有大小限制。GET的大小非常有限(最多4K)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3260827|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|$]]

For JSON data, it's much easier to POST it as "application/json" content-type. If you use GET, you have to URL-encode the JSON in a parameter and it's kind of messy. Also, there is no size limit when you do POST. GET's size if very limited (4K at most).

blocks|key|3047109|text|实际上，php://input允许你读取原始的POST数据。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3047110|它是$HTTP_RAW_POST_DATA的内存消耗较少的替代方案，并且不需要任何特殊的php.ini指令。|BOLD|3047111|enctype="multipart/form-data"不提供php://input。|3047112|参考：+http://php.net/manual/en/wrappers.php.php|3047113|entityMap|0|LINK|mutability|MUTABLE|url|http://php.net/manual/en/wrappers.php.php^0|4|B|0|0|1H|0|0|T|W|B|0|0|3|4|15|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|K|3|L|5|6|7|15|8|@$9|16|A|17|B|H]]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|M|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

Actually <code>php://input</code> allows you to read raw POST data.

It is a less memory intensive alternative to $HTTP_RAW_POST_DATA and does not need any special php.ini directives.

<code>php://input</code> is not available with <code>enctype="multipart/form-data"</code>.

Reference: <a href="http://php.net/manual/en/wrappers.php.php" rel="noreferrer">http://php.net/manual/en/wrappers.php.php</a>

blocks|key|3047122|text|input+php://+|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3047123|是一个只读流，允许您从请求体读取原始数据。在POST请求的情况下，最好使用php://输入而不是$HTTP_RAW_POST_DATA，因为不依赖于特殊的php.ini指令。此外，对于那些默认情况下不填充$HTTP_RAW_POST_DATA的情况，与激活always_populate_raw_post_data相比，它可能是一种内存密集度较低的替代方案。|blockquote|offset|length|style|BOLD|3047124|3047125|3047126|来源：http://php.net/manual/en/wrappers.php.php。|3047127|entityMap|0|LINK|mutability|MUTABLE|url|http://php.net/manual/en/wrappers.php.php^0|0|3|2|1Y|G|0|0|0|3|15|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@$E|W|F|X|G|H]|$E|Y|F|Z|G|H]]|9|@]|A|$]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|12|8|@]|9|@$E|13|F|14|1|15]]|A|$]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

<blockquote>
 php://input is a read-only stream that allows you to read raw data
 from the request body. In the case of POST requests, it is preferable
 to use php://input instead of $HTTP_RAW_POST_DATA as it does not
 depend on special php.ini directives. Moreover, for those cases
 where $HTTP_RAW_POST_DATA is not populated by default, it is a
 potentially less memory intensive alternative to activating
 always_populate_raw_post_data.
</blockquote>

Source: <a href="http://php.net/manual/en/wrappers.php.php" rel="noreferrer">http://php.net/manual/en/wrappers.php.php</a>.

blocks|key|309053|text|file_get_contents(php://input)+-获取原始的POST数据，当您编写API并需要XML/JSON/...时，需要使用它。一些不能被PHP解码成$_POST的输入示例：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|309054|通过邮寄JSON字符串发送|309055|<input+type="button"+value=+"click"+onclick="fn()">
<script>
+function+fn(){


++++var+js_obj+=+{plugin:+'jquery-json',+version:+2.3};

++++var+encoded+=+JSON.stringify(+js_obj+);

var+data=+encoded


++++$.ajax({
++type:+"POST",
++url:+'1.php',
++data:+data,
++success:+function(data){
++++console.log(data);
++}

});

++++}
</script>|code-block|syntax|javascript|309056|1.php|309057|//print_r($_POST);+//empty!!!+don't+work+...+
var_dump(+file_get_contents('php://input'));|309058|entityMap^0|0|2A|0|0|0|0|5|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|R|$]]

file_get_contents(php://input) - gets the raw POST data and you need to use this when you write APIs and need XML/JSON/... input that cannot be decoded to $_POST by PHP
some example : 

send by post JSON string 

<pre><code>&lt;input type="button" value= "click" onclick="fn()"&gt;
&lt;script&gt;
 function fn(){


 var js_obj = {plugin: 'jquery-json', version: 2.3};

 var encoded = JSON.stringify( js_obj );

var data= encoded


 $.ajax({
 type: "POST",
 url: '1.php',
 data: data,
 success: function(data){
 console.log(data);
 }

});

 }
&lt;/script&gt;
</code></pre>

1.php

<pre><code>//print_r($_POST); //empty!!! don't work ... 
var_dump( file_get_contents('php://input'));
</code></pre>

<code>file_get_contents("php://input")</code> or <code>$HTTP_RAW_POST_DATA</code> - which one is better to get the body of JSON request?

And which request type (<code>GET</code> or <code>POST</code>) should I use to send JSON data when using client side <code>XmlHTTPRequest</code>?

My question was inspired from this answer:
<a href="https://stackoverflow.com/questions/813487/how-to-post-json-to-php-with-curl/813512#813512">How to post JSON to PHP with curl</a>

Quote from that answer:

<blockquote>
 From a protocol perspective <code>file_get_contents("php://input")</code> is actually more correct, since you're not really processing http multipart form data anyway.
</blockquote>

file_get_contents("php://input") or $HTTP_RAW_POST_DATA, which one is better to get the body of JSON request?

数据库

服务器

jQuery

JSON

file_get_contents("php://input")或$HTTP_RAW_POST_DATA -哪个更适合获取JSON请求的正文？在使用客户端XmlHTTPRequest时，我应该使用哪种请求类型(GET或POST)来发送JSON数据我的问题的灵感来自于这个答案：引述自该答案：从协议的角度来看，file_g...

问file_get_contents("php://input")和$HTTP_RAW_POST_DATA，哪个更适合获取JSON请求的正文？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问file_get_contents("php://input")和$HTTP_RAW_POST_DATA，哪个更适合获取JSON请求的正文？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问file_get_contents("php://input")和$HTTP_RAW_POST_DATA，哪个更适合获取JSON请求的正文？
EN