[GH-ISSUE #159] custom curl options by user #102

New issue

Closed

opened 2026-02-27 19:26:05 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 19:26:05 +03:00

Owner

Originally created by @csimpi on GitHub (Jun 21, 2019).
Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/159

Hi,
thx for your awesome work!

I'd like to set some curl options. I can't change Request.php in the vendor folder for obvious reason.
Is it possible to set/overwrite the $options array from my code? If it's not it would be an awesome (and must-have) feature.

Currently, I'm getting timeout error messages randomly when I'm connecting to api.spotify.com, I'd need to set the curl connection timeout option and fine-tune the request-response frequency.

Originally created by @csimpi on GitHub (Jun 21, 2019). Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/159 Hi, thx for your awesome work! I'd like to set some curl options. I can't change `Request.php` in the `vendor` folder for obvious reason. Is it possible to set/overwrite the `$options` array from my code? If it's not it would be an awesome (and must-have) feature. Currently, I'm getting timeout error messages randomly when I'm connecting to api.spotify.com, I'd need to set the curl connection timeout option and fine-tune the request-response frequency.

kerem

2026-02-27 19:26:05 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-27 19:26:06 +03:00

Author

Owner

@csimpi commented on GitHub (Jun 22, 2019):

A quick workaround, using Guzzle instead of curl with this adapter:
https://github.com/andig/spotify-web-api-extensions

@csimpi commented on GitHub (Jun 22, 2019): A quick workaround, using Guzzle instead of curl with this adapter: https://github.com/andig/spotify-web-api-extensions

kerem commented

2026-02-27 19:26:06 +03:00

Author

Owner

@jwilsson commented on GitHub (Jun 26, 2019):

Hey!
Sorry for the late answer!

Sounds like a valid use case, I'll take a look at it over the weekend.

@jwilsson commented on GitHub (Jun 26, 2019): Hey! Sorry for the late answer! Sounds like a valid use case, I'll take a look at it over the weekend.

kerem commented

2026-02-27 19:26:06 +03:00

Author

Owner

@csimpi commented on GitHub (Jun 26, 2019):

@jwilsson
Thank you!
I think the best way would be making an adapter for the curl part with an opportunity to use any kind of external HTTP Clients.

Also, I'd recommend using Guzzle instead of curl. Curl has a lot of problems on several servers, lots of memory leaking problems, etc. Now that I have overridden the Request class and using Guzzle HTTP every other random issue has been disappeared (even behind a proxy).

@csimpi commented on GitHub (Jun 26, 2019): @jwilsson Thank you! I think the best way would be making an adapter for the curl part with an opportunity to use any kind of external HTTP Clients. Also, I'd recommend using Guzzle instead of curl. Curl has a lot of problems on several servers, lots of memory leaking problems, etc. Now that I have overridden the Request class and using Guzzle HTTP every other random issue has been disappeared (even behind a proxy).

kerem commented

2026-02-27 19:26:06 +03:00

Author

Owner

@jwilsson commented on GitHub (Jun 27, 2019):

@csimpi Absolutely, I agree! It's definitely something I've thought about and will look into for the next major release.

@jwilsson commented on GitHub (Jun 27, 2019): @csimpi Absolutely, I agree! It's definitely something I've thought about and will look into for the next major release.