-
Notifications
You must be signed in to change notification settings - Fork 471
Set curl timeout in config #351
Comments
Not sure which all options we'd want to set in the config rather than in more specific locations. Potential targets:
Less clear to me whether CURLOPT_NOBODY makes sense, or CURLOPT_INTERFACE which I think is only used once |
I preffer using 30 seconds for timeout on my localhost as I have very lagging net connection. So, timeout option should be added. As for
I don't think anyone would need these to be reconfigured. |
I'm improving our HTTP client atm and will tackle this issue. I recommend to let this options define via config:
And we have also a few calls of |
Based on the Guzzle request options I would recommend the following names in config that will be set to the HTTP client:
|
@Art4 Is this something you are working on as you rework some of the underlying use of curl, or is it already done? |
@jeckman I'm not actively working on this atm, but the plan is to rework all curl functions into the CurlClient. |
Today there are a number of places where the curl option for timeout ( CURLOPT_TIMEOUT, CURLOPT_CONNECTTIMEOUT ) gets set to various values.
Ideally, on could set that in the config file and have it applied.
Impacted:
/src/Http/CurlClient.php line 85, which currently sets CURLOPT_CONNECTTIMEOUT to 3.
/src/Provider/Youtube/SignatureDecipher.php line 323 which sets CURLOPT_TIMEOUT to 10.
/src/Application/ControllerAbstract.php line 92, which sets CURLOPT_TIMEOUT to 3.
/src/Application/DownloadController.php line 199, which sets CURLOPT_TIMEOUT to 50.
Granted some of these are for different purposes, but it feels like we need a more clear single place to set all the CURLOPT stuff
The text was updated successfully, but these errors were encountered: