HTTP_Request2_ConnectionException since v2.4.0 #20
Assignees
Comments
|
UPDATE: It seems that it could have something to do with the following line: // Run socket in non-blocking mode, to prevent possible problems with
// HTTPS requests not timing out properly (see bug #21229)
stream_set_blocking($this->socket, false);in File When I comment out this line with |
|
Oops, looks like it's even mentioned in PHP doc comments Thanks for the report, will fix ASAP. |
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this issue
Oct 4, 2020
Update pear-HTTP_Request2 package to 2.4.2. Update 2.4.2 (2020-09-24 18:13 UTC) Changelog: Socket adapter could prematurely end receiving the response body due to fread() call returning an empty string 2.4.1 (2020-08-01 05:16 UTC) Changelog: Switch socket to blocking mode when enabling crypto, this fixes HTTPS requests through proxy with Socket adapter pear/HTTP_Request2#20 2.4.0 (2020-07-26 13:43 UTC) Changelog: * Minimum required version is now PHP 5.6, as using older versions for HTTPS requests may be insecure * Removed support for magic_quotes_runtime, as get_magic_quotes_runtime() was deprecated in PHP 7.4 and the functionality itself was disabled since PHP 5.4 (bug #23839) * Socket adapter now uses socket in non-blocking mode, as some configurations could have problems with timeouts in HTTPS requests (bug #21229) * Fixed bogus size check error with gzipped responses larger than 4 GiB uncompressed (bug #21239) * Use current "Intermediate compatibility" cipher list * Updated Public Suffix List The package is now 100% autoload-compatible, when installed with composer it no longer uses include-path and does not contain require_once statements
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
since updating to
v2.4.0we have problems connecting from our local docker-environment to external APIs through our network proxy.We receive a message
Failed to enable secure connection when connecting through proxywhen connecting.With
v2.3.0everything worked fine (with our exact same proxy configuration)Unfortunately I can't give some more hints.
Can somebody investigate this problem or give any workaround?
Regards
Andy
The text was updated successfully, but these errors were encountered: