S3-Assembly with s3/cache-control-header won't finish

Archived from the Transloadit support forum. Originally posted on February 21, 2012; details may be outdated, see our docs for current behavior. Original thread

I modified a so far working template so s3-headers would be set:
[…]

  "headers": {
      "Content-Type": "${file.mime}",
      "Cache-Control": "max-age=315360000",
      "FileURL":"${file.url_name}"
  },

[…]

The Assembly won’t finish (after 5min with only one image, I canceled the job).

See Assembly REDACTED

Well if the assembly does not throw an error, you should not cancel it.

We sometimes have unpredicted high load which cause elevated queue times.
For images, you should give it at least 5 to 10minutes time.

I just got the same result:

Test 1: with s3/“header”
Objekt: 1 Image… not finishing after >10min (still running now)
Template REDACTED
Assembly REDACTED

Test 2: without s3/“header”
Objekt: Same Image… done in 3 seconds
Template REDACTED
Assembly REDACTED

The only difference is the used template with/without the “header”-attributes.

The assembly failed after 12min with S3_STORE_CONFIRMATION_FAILURE

See Assembly REDACTED

Any clue what went wrong?

Hey rtl,

sorry for the delayed response. It seems this was an amazon problem.

This is the error that was logged (coming from amazon …):

“The stored file did not show up in the S3 bucket, even so multiple attempts have been made to store it. Amazon has a bad day : /”.

I am sorry about this, but I have to ask you to replay the assembly. : /

Kind regards,
Tim

Thank you for getting back to me.

Current test with in both cases the same file - no change in behaviour:
Assembly REDACTED, still running
Assembly REDACTED, completed after 3 sec

Am I doing anything wrong in my template? Maybe I choose max-age to big with 315360000?

At the moment your website isn’t responding for me. So I have to test this later.

Doesn’t work with lower max-age-values: e.g. “max-age=3153600”

see Assembly REDACTED

I just looked into this, but I’m not entirely sure what is going on yet. What’s the FileURL header you are setting for? Does the problem occur when not specifying that header?

--fg

That’s it. In removing the FileURL header the problem disappeared. Thank you.