RCA: Failure to pay attention to the HTTP/1.1 characteristics of Curl-library Post when it is above 1024 bytes leads to HessianPHP transmission_PHP tutorial

First list the error messages of HessianPHP:

---

Basic knowledge background: 1) The ins and outs of “Expect: 100-continue”: The purpose of designing the 100 (Continue) HTTP status code in the HTTP/1.1 protocol is that before the client sends a Request Message, the HTTP/1.1 protocol allows the client to first determine whether the server is willing to accept the message body sent by the client (based on Request Headers ). That is, Client and Server allow both parties to "handshake" before Posting (larger) data. If they match, the Client will start sending (larger) data. The reason for this is that if the client directly sends the request data, but the server rejects the request, this behavior will cause a lot of resource overhead. ​ The protocol requirements for HTTP/1.1 clients are:

header field! ​

2) libcurl enables the "Expect:100-continue' feature when sending data larger than 1024 bytes:

1. Send a request, including an "Expect: 100-continue" header field, asking the Server if it is willing to receive data; 2. After receiving the 100-continue response returned by the Server, the data is POSTed to the Server;

zxgfa added in 2012:

(Zheng Yun's Note 1: lighttpd Version 1.4 had this serious problem, which was fixed in version 1.5. Zheng Yun Note 2: Resin added support for Expect: 100-continue in version 3.0.5. )

3) PHP Curl-library can actively block this feature: Someone left a message under PHP Manual::curl_setopt : PHP curl complies with the characteristics of libcurl. Since not all web servers support this feature, various errors can occur. If you encounter this, you can use the following command to block the "Expect" header field: <span class="html"><span class="default"> <?php <code><span class="html"><span class="default">    <?php </span></span></span></span></span><span class="html"><span class="default">    curl_setopt</span><span class="keyword">(</span><span class="default">$ch</span><span class="keyword">,<span class="Apple-converted-space"> </span></span><span class="default">CURLOPT_HTTPHEADER</span><span class="keyword">, array(</span><span class="string">'Expect:'</span><span class="keyword">));<br></span><span class="default">    ?><br></span><span pooy><br></span></span> <span class="html"><span class="default"> curl_setopt<img class="decoded" src="RCA:%20Failure%20to%20pay%20attention%20to%20the%20HTTP/1.1%20characteristics%20of%20Curl-library%20Post%20when%20it%20is%20above%201024%20bytes%20leads%20to%20HessianPHP%20transmission_PHP%20tutorial" alt="RCA: Failure to pay attention to the HTTP/1.1 characteristics of Curl-library Post when it is above 1024 bytes leads to HessianPHP transmission_PHP tutorial"><span class="keyword">(<hr> <span class="default">$ch<strong><span class="keyword">,</span></strong> <ul> <li><span class="default">CURLOPT_HTTPHEADER</span></li> <span class="keyword">, array(</span> </ul> <span class="string"> 'Expect:'<hr> <span class="keyword">));<strong></strong><span class="default"> ?><br><blockquote hessian post><span the pooy sample code is as follows:><strong></strong></span></blockquote></span></span></span></span></span></span></span>  

---

Figure 1 You can convince PHP's curl backend to stop doing the 100-continue-thing by setting an explicit request header ​

---

Other knowledge background:

According to the HessianTransport code, "Hessian request using the CURL library".

Problem:

, and Hessian reports an error "CURL transport error: transfer closed with outstanding read data remaining". ​ Solution: Modify the CURLOPT item in hessian: CURLOPT_HTTPHEADER => array("Content-Type: application/binary") Change to CURLOPT_HTTPHEADER => array("Content-Type: application/binary","Expect:") p.s.: Some people think that changing to the HTTP/1.0 protocol can bypass this 100-continue problem, but this is just a sign of weakness by engineers who are unwilling to understand the principle. ​ Reference resources: 1) 2011, Laruence, Expect:100-continue; 2) PHP manual, If you are doing a POST, and the content length is 1,025 or greater; 3) HTTP 1.1 RFC, Use of the 100 (Continue) Status; 4) stackoverflow, 2009, PHP HTTP POST fails when cURL data > 1024; 5) zxgfa, 2012, libcurl usage problem "Expect100-continue"; 6) lighttpd, 2009, 'Expect' header gives HTTP error 417; A few complimentary pictures: Ask the donor to take it: 360 degree backflip kickoff: 360 no dead ends: ​

http://www.bkjia.com/PHPjc/440146.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/440146.htmlTechArticleFirst list the error messages of HessianPHP: Basic knowledge background: 1) The ins and outs of Expect: 100-continue: HTTP/ 1.1 The purpose of designing the 100 (Continue) HTTP status code in the protocol is to...