In some cases, access to s3 servers may be blocked by a firewall. When this happens the reports/status page may time out rather than surfacing an error message.

This patch, which applies on top of #2271881: Additional status report warnings , adds a configurable cURL timout for status checks.

CommentFileSizeAuthor
configurable-curl-timeout.patch1.05 KBdrnikki
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

deviantintegral’s picture

deviantintegral CreditAttribution: deviantintegral at Lullabot for NBCUniversal commented
Version: 7.x-1.0 » 7.x-2.x-dev

Thanks for the patch. This makes sense to me, given that Guzzle defaults to no timeout and Drupal defaults to a 30 second timeout.

Rather than expose another UI option, I think I'll just set our client to default to 30 seconds.

deviantintegral’s picture

deviantintegral CreditAttribution: deviantintegral at Lullabot for NBCUniversal commented
Status: Active » Needs review

PR opened at https://github.com/justafish/drupal_amazons3/pull/20

Note that it's a *connect* timeout explicitly, since cURL could be downloading or uploading a large file from S3 that could take any amount of time.

deviantintegral’s picture

deviantintegral CreditAttribution: deviantintegral at Lullabot for NBCUniversal commented
Status: Needs review » Fixed

  • deviantintegral committed b9a71e3 on 7.x-2.x 
    Issue #2289205: Set a 30 second cURL connect timeout by default.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.