Cloudfront Error 28 Operation Timed Out
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies
Curl Error 28 Operation Timed Out
of this site About Us Learn more about Stack Overflow the company Business error code 28 operation timed out Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask
Vudu Error Code 28 Operation Timed Out
Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign vudu error code 28 operation timed out roku up Strange timeout with PHP cURL and SSL up vote 2 down vote favorite I'm experiencing strange timeouts using cURL with PHP when trying to access Amazon Cloudfront. This seems to affect all invalidation requests, creating distributions etc. cURL either reports receiving 0 bytes, or very few bytes, and then time-out: Operation timed out after 120000 milliseconds with 88 out of 619 operation timed out error in chrome bytes received. Extending the timeout settings does not seem to make a difference. Putting a trace using CURLOPT_VERBOSE produces this output: * About to connect() to cloudfront.amazonaws.com port 443 (#0) * Trying 72.21.215.67... * connected * Connected to cloudfront.amazonaws.com (72.21.215.67) port 443 (#0) * skipping SSL peer certificate verification * SSL connection using SSL_RSA_WITH_RC4_128_MD5 * Server certificate: * subject: CN=cloudfront.amazonaws.com,O=Amazon.com Inc.,L=Seattle,ST=Washington,C=US * start date: Jul 30 00:00:00 2010 GMT * expire date: Jul 29 23:59:59 2013 GMT * common name: cloudfront.amazonaws.com * issuer: CN=VeriSign Class 3 Secure Server CA - G2,OU=Terms of use at https://www.verisign.com/rpa (c)09,OU=VeriSign Trust Network,O="VeriSign, Inc.",C=US > POST /2010-11-01/distribution/E1CIM4A92QFD98/invalidation HTTP/1.1 User-Agent: S3/php Accept: */* Host: cloudfront.amazonaws.com Date: Wed, 07 Mar 2012 14:31:58 GMT Content-Type: application/xml Authorization: AWS ************************ Content-Length: 200 < HTTP/1.1 201 Created < x-amzn-RequestId: 4c2d0d3f-6862-11e1-ac27-5531ac8c967f < Location: https://cloudfront.amazonaws.com/2010-11-01/distribution/E1CIM4A92QFD98/invalidation/I35KLNROKA40FU * Operation timed out after 120000 milliseconds with 0 bytes received * Closing connection #0 This seems similar to this question. However, it looks like in my case curl does in fact get a response, but somehow ignores it and times-out? From what I see, the response is received (201 Created...), and the
connections all over the world. Join today Download & Extend Drupal Core Distributions Modules Themes FeedsIssues Feeds: cURL error (28) Operation timed
Curl Error 28 Operation Timed Out After
out after X milliseconds with 0 bytes received ActiveProject:FeedsVersion:7.x-2.x-devComponent:DocumentationPriority:NormalCategory:Bug reportAssigned:UnassignedReporter:kwaddelCreated:April 26, operation timed out after milliseconds with 0 bytes received 2012 - 22:45Updated:March 4, 2016 - 23:53 Log in or register to update this issue Jump to:Most
Curl Operation Timed Out After Milliseconds
recent comment Hi, I'm pretty new to Drupal and the Drupal forums so I was unable to find anything directly related to this or anything that would help. What http://stackoverflow.com/questions/9603641/strange-timeout-with-php-curl-and-ssl we are trying to do is link in a news feed from a central news location. So the users submit their news to our news site and based on the tags that news story is sent to the right feed. It has been working but recently one of the pages won't update with the new info. I went https://www.drupal.org/node/1549740 in and looked to make sure that their info was actually being tagged properly and it is and I can see all of it in the XML, but the URL to link to their feed was gone. When I tried to put it back in I got the error above. If I resubmit it again right away it goes through but gives a different error and doesn't update anything. If someone could point me in the right direction or something that would be great. Comments Comment #1 kwaddel CreditAttribution: kwaddel commented May 18, 2012 at 5:30pm Status: Active » Closed (fixed) Log in or register to post comments Comment #2 jenlampton CreditAttribution: jenlampton commented September 4, 2013 at 1:06am Component: Feeds News » Code @kwaddel why was this issue closed? Did you figure it out? if you did could you post your solution here for the rest of us? :) Log in or register to post comments Comment #3 jenlampton CreditAttribution: jenlampton commented September 4, 2013 at 1:06am Component: Code Â