Hi there,

On our development servers we have been using the s3_directive to override our HeyWatch account settings and upload encoded videos to a test S3 bucket. This has been working for some time via a standard HTML form POST, but I have been updating the upload process to make use of SWFUpload which now uses the REST API at http://heywatch.com/upload.xml instead of the HTML form POST at http://heywatch.com/upload.

When using the REST /upload.xml API the s3_directive doesn’t seem to be picked up so our encoded videos go through to our production S3 bucket instead of the supplied S3 bucket.

Could you let me know if this is a bug and if so when it would likely to be fixed?

Many Thanks,

Tim

It should work as expected. Check if the s3 directive is sent correctly.

Yes your right. The problem seemed to be with using addPostParam on SWFUpload, which didn’t actually add the parameter so it wasn’t obvious.

Thanks