- Issue created by @xenophyle
In 🐛 Mailchimp client does not respect the api_timeout anymore Fixed , szeidler reported that the api_timeout setting was no longer working. That has been fixed at a basic level but additional suggestions included
Because of #2768455: High cURL timeout can lead to Denial of Service → , when the api_timeout was initially introduced it's not recommended to set the timeout to a high value. Especially when you use a subscription block and the Mailchimp server responds slow (and Drupal cache is cleared).
Therefore it might be better, if could configure overwrite a custom timeout for different use-cases. For subscriptions blocks a short timeout is preferable, but when using extensive API calls like the ones described above, we like to set a higher one. Currently there is no possibility to do so, even on the mailchimp-api-php side, because the guzzle client is hidden behind a private property.
Active
2.0
General