You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The correct proxy syntax is not consistent across handlers. This is problematic, because certain request options automatically switch to another handler (namely stream).
The proxy syntax should be normalized. The http://<host>:<port> one from cURL probably is the canonical one.
cURL should support streaming responses.
Additional context
This is problematic for my use case, because I provide a factory that returns Guzzle clients that are readily configured to use a proxy. This factory cannot know whether the user of this client will request a streaming response or not. Streaming responses might be required to properly consume only the first few bytes of a response for URL unfurling if the remote end might be an infinite stream (e.g. a web radio).
The text was updated successfully, but these errors were encountered:
This issue probably is a duplicate of #2616. But that one is marked stale, without any responses and I believe it lacks some detail I was able to provide.
Guzzle version(s) affected: Current git master (3a0543e / 7.2.0)
PHP version: 7.4.12
cURL version: 7.64.0
Description
The correct proxy syntax is not consistent across handlers. This is problematic, because certain request options automatically switch to another handler (namely
stream
).How to reproduce
Running this script against Tinyproxy:
With
HTTP_PROXY=http://127.0.0.1:8888
:With
tcp://127.0.0.1:8888
Possible Solution
http://<host>:<port>
one from cURL probably is the canonical one.Additional context
This is problematic for my use case, because I provide a factory that returns Guzzle clients that are readily configured to use a proxy. This factory cannot know whether the user of this client will request a streaming response or not. Streaming responses might be required to properly consume only the first few bytes of a response for URL unfurling if the remote end might be an infinite stream (e.g. a web radio).
The text was updated successfully, but these errors were encountered: