Databases
StackOverflow2013
Postsdbo
POPHP Curl timeout, but unix Curl don't
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPHP Curl timeout, but unix Curl don't
    primarykey
    data
    text
    <p>--- Update at the bottom, it's related to CURLOPT_COOKIE --</p> <p>I'm developping on my local machine ( 192.168.1.103 ), and I have a PHP script that makes a CURL call to get the header and the content returned by a remote script.</p> <p>I've installed 2 copies of the remote script that must return his content:<br> - One on my local machine, under the same virtual host. ( <a href="http://192.168.1.103/test/output_script.php" rel="nofollow">http://192.168.1.103/test/output_script.php</a> )<br> - One on a remote server. ( <a href="http://site.com/text/outputscript.php" rel="nofollow">http://site.com/text/outputscript.php</a> )</p> <p>The CURL script works really well when I try to get the content from the remote server, but completly timeout when trying to get the content from the local server.</p> <p>The verbose of the PHP CURL is:</p> <pre><code>* About to connect() to 192.168.1.103 port 80 (#0) * Trying 192.168.1.103... * connected * Connected to 192.168.1.103 (192.168.1.103) port 80 (#0) &gt; GET /app/getContent HTTP/1.1 Host: 192.168.1.103 Accept: */* Cookie: PHPSESSID=u8spbervheh3tcrv62gcnc2j72 * Operation timed out after 5001 milliseconds with 0 bytes received * Closing connection #0 </code></pre> <p>Note that the URI is rewrited with the following .htaccess file (on both location):</p> <pre><code>RewriteEngine on RewriteBase /cms/client1/public_html RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule .* index.php [L] </code></pre> <p>Also note that I've activated the rewrite log and compared request to make sure that the mod_rewrite action was exactly the same in all situation. ( I'm 100% sure it's not a rewrite trouble ) </p> <p>If I try to get the file using the CURL app under Ubuntu, it works well:</p> <pre><code>$ curl -v --cookie PHPSESSID=u8spbervheh3tcrv62gcnc2j72 http://192.168.1.103/app/getContent * About to connect() to 192.168.1.103 port 80 (#0) * Trying 192.168.1.103... connected * Connected to 192.168.1.103 (192.168.1.103) port 80 (#0) &gt; GET /app/getContent HTTP/1.1 &gt; User-Agent: curl/7.21.0 (i686-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18 &gt; Host: 192.168.1.103 &gt; Accept: */* &gt; Cookie: PHPSESSID=u8spbervheh3tcrv62gcnc2j72 &gt; &lt; HTTP/1.1 403 Forbidden &lt; Date: Thu, 24 Feb 2011 21:40:17 GMT &lt; Server: Apache/2.2.16 (Ubuntu) &lt; X-Powered-By: PHP/5.3.3-1ubuntu9.3 &lt; Expires: Thu, 19 Nov 1981 08:52:00 GMT &lt; Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 &lt; Pragma: no-cache &lt; Vary: Accept-Encoding &lt; Content-Length: 82 &lt; Content-Type: text/html; charset=UTF-8 &lt; * Connection #0 to host 192.168.1.103 left intact * Closing connection #0 WT_AUTH non défini. (strictement aucune authentification actuellement en session) </code></pre> <p>The 403 error and the WT_AUTH content is what I expect to receive instead of the timeout that I have with PHP.<br> It's also the same (wanted &amp; correct) result that I receive if use the php curl on the remote server:</p> <pre><code>* About to connect() to site.com port 80 (#0) * Trying 123.123.123.123... * connected * Connected to site.com (123.123.123.123) port 80 (#0) &gt; GET /app/getContent HTTP/1.1 Host: site.com Accept: */* Cookie: PHPSESSID=u8spbervheh3tcrv62gcnc2j72 &lt; HTTP/1.1 403 Forbidden &lt; Date: Thu, 24 Feb 2011 21:45:30 GMT &lt; Server: Apache/2.2.16 (Debian) DAV/2 SVN/1.6.12 mod_fcgid/2.3.6 &lt; Expires: Thu, 19 Nov 1981 08:52:00 GMT &lt; Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 &lt; Pragma: no-cache &lt; Content-Length: 28 &lt; Content-Type: text/html; charset=UTF-8 &lt; * Connection #0 to host site.com left intact * Closing connection #0 </code></pre> <p>And I'll also get the same thing if I access directly 192.168.1.103/app/getContent in my browser. </p> <p>Finally, I've also made sure that the getContent script was working by putting logs in it. The weird part is that if I start the request at 16:45:00, and the timeout occur at 16:45:05, the logged data from the getContent script will be dated at 16:45:05. So it's like if the CURL was maintaining a connexion in the "opening" state. And when the connexion is closed, the php script is allowed to start. </p> <p>Any idea of my it doesn't work locally ?</p> <p>In case you want to take a look at the PHP code, here's the pertinent part:</p> <pre><code>$ressource = curl_init(); curl_setopt($ressource, CURLOPT_URL, $destinationUrl); curl_setopt($ressource, CURLOPT_VERBOSE, true); $handle = fopen(FRAMEWORK_ROOT . DIRECTORY_SEPARATOR . 'log' . DIRECTORY_SEPARATOR . 'curl_debug.txt', 'w'); curl_setopt($ressource, CURLOPT_STDERR, $handle); // Turn off the server and peer verification (TrustManager Concept). curl_setopt($ressource, CURLOPT_SSL_VERIFYPEER, FALSE); curl_setopt($ressource, CURLOPT_SSL_VERIFYHOST, FALSE); curl_setopt($ressource, CURLOPT_RETURNTRANSFER, TRUE); //retourn content curl_setopt($ressource, CURLOPT_HEADER, TRUE); //get HTTP headers curl_setopt($ressource, CURLOPT_COOKIE, session_name() . '=' . session_id()); curl_setopt($ressource, CURLOPT_TIMEOUT, 5); echo "\n&lt;br /&gt;" . date('Y/m/d H:i:s'); $httpResponse = curl_exec($ressource); echo "\n&lt;br /&gt;" . date('Y/m/d H:i:s'); if(curl_errno($ressource) != 0) throw new Core_Exc_Def(curl_error($ressource)); // WILL THROW AN ERROR ON 192.168.1.103, BUT NOT ON THE REMOTE SITE. </code></pre> <p>Funny fact: before adding the TIMEOUT, the loading was infinite. The local site wasn't responding, even other pages. I needed to restart the apache server to be able to access the site again...</p> <p>Update:<br> If I comment the line:</p> <pre><code>curl_setopt($ressource, CURLOPT_COOKIE, session_name() . '=' . session_id()); </code></pre> <p>It's "working" (it cause another problem, but nothing related to the timeout). Both script are on the same virtual host, and share the same session, but that should not create a CURL TimeOut ?!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USFMaz008
    1. USFMaz008
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload