Bug #69777 [Opn]: 502 Bad Gateway when getting response
Edit report at https://bugs.php.net/bug.php?id=69777&edit=1
ID: 69777
User updated by: sb at firstvector dot org
Reported by: sb at firstvector dot org
Summary: 502 Bad Gateway when getting response
Status: Open
Type: Bug
Package: FPM related
Operating System: OS X Yosemite 10.10.3 (14D136)
-PHP Version: 5.6.9
+PHP Version: 5.6.9, 5.6.10
Block user comment: N
Private report: N
New Comment:
Bug still reproduced on 5.6.10
Previous Comments:
------------------------------------------------------------------------
[2015-06-08 21:03:54] sb at firstvector dot org
Description:
------------
Using PHP-FPM 5.6.9 I've getting the error while working with cURL, for example. When I
commented the code that does remote requests then everything's fine, otherwise error log
contains an errors like:
upstream prematurely closed connection while reading response header from upstream, client:
127.0.0.1, server: unga.loc, request: "GET / HTTP/1.1", upstream:
"fastcgi://127.0.0.1:9000", host: "unga.loc", referrer: "http://unga.loc/content/test-project-4"
For solving this problem I've tried to use UNIX socket and TCP connection - no result. So,
I've think that is an error.
Used software:
nginx 1.8.0 (also tested on 1.6.3)
php-fpm 5.6.9 (works fine on 5.6.7)
Test script:
---------------
// Execution of this (and similar) code will ends by 502 error.
$ch = curl_init('https://php.net');
curl_setopt_array($ch, [
CURLOPT_HTTPGET => true,
CURLOPT_RETURNTRANSFER => true,
]);
$response = curl_exec($ch);
curl_close($ch);
var_dump($response);
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=69777&edit=1
Thread (8 messages)