Comments on: Uploading to S3 with a FileReference from Flex 3 on OS X

By: ben

ben — Wed, 27 Oct 2010 17:25:44 +0000

The problem is not so much with the 200 / 201 response — I can just write a body to those responses and Flash is OK with that — but with the 100 Continue response, which Flash just doesn’t seem to like no matter what.

By: ben

ben — Wed, 27 Oct 2010 00:44:24 +0000

I’m having the same problem uploading via YUI Uploader, which is extra fun because it looks like now I have to open up the source and add some error handling so this #2038 error doesn’t interfere with the upload flow.

By: Sean

Sean — Mon, 20 Sep 2010 16:37:27 +0000

I’m having the multi-file upload issue in random browsers across different OSs (specifically FF and Flock in Windows). I’ve modifying an uploader that someone else built and uses AS2. Any idea how I can set up strong event listener references in AS2? Having trouble finding the right info on google.

Any help would be greatly appreciated. I’m not overly experienced in flash and it looks like I am the happy recipient of someone else’s problem :/

By: pam

pam — Wed, 16 Jun 2010 11:57:16 +0000

On nginx was getting this error for files greater then 1mb. Fixed using the client_max_body_size directive.

By: Mauricio Arango

Mauricio Arango — Thu, 24 Sep 2009 21:51:22 +0000

Hi,
Thanks for your post. I have spend countless hours with a related problem.
The most basic fileupload example from the Adobe AS3 Flash CS4 reference doesn’t work in my localhost (os X – Apache). I just realize the example works flawlessly once uploaded to a server and tested there.

I’m afraid of implementing an flash uploader on a commercial project. I don’t know when it will work and when it wont.

I wonder if you would be so kind to describe an answer to address this issue. I’ve been 2 nights without sleep because of this problem.

How can we make sure a fileupload works on most servers? the solution will have to be on the client side because many shared servers don’t allow much tailoring with their settings.

Thanks so much.

By: John Pencola

John Pencola — Wed, 27 May 2009 19:46:36 +0000

Thanks for the elaboration! This had me going today trying to track down why I kept getting all those IOErrorEvents even though the uploads were successful One suggestion ( based off the commented AWS code ) is to still handle IOErrorEvents but just do nothing… since based on the Flex/Flash language reference the HTTPStatusEvent always fires prior to an IOErrorEvent, you can do you forked logic there, like so (simplified for readability):
——————————————————

function onUploadIOError( _event: IOErrorEvent ): void {};

function onUploadHTTPStatus( _event: HTTPStatusEvent ): void
{
if ( _event.status == 200 || _event.status == 201 )
{
// do upload completed logic…
}
else
{
// do error logic…
}
}
—————————————-
using this approach you don’t have to keep a flag for checking across methods. Thanks again!

By: Neethu

Neethu — Mon, 30 Mar 2009 10:32:50 +0000

Hi Thanks for the blog. We were struggling with this issue for two days and atlast search in google took us to your blog.Your tips helped us a lot in solving the issue.

By: Rob

Rob — Mon, 21 Jul 2008 10:08:55 +0000

I tried adding this to the policy and I’m getting a security error as well.

// mac fix
buffer.push(“['eq', '$success_action_status', '201'],”);

By: tad

tad — Thu, 26 Jun 2008 03:33:24 +0000

Hi thanks for the notes. I have been struggling with this most of the day. I am getting a security 2049 error. I have a cross domain file in s3. I’m using Vista. I can do it with the form and I already found the 201 xml return status thing, but it is sure frustrating.

By: Simple Rails Uploader | Nuclear Rooster

Simple Rails Uploader | Nuclear Rooster — Thu, 10 Apr 2008 16:26:55 +0000

[...] was recently trying to implement an upload to Amazon S3, and it wasn’t working. I couldn’t tell if it was the Flex front end, or the S3 [...]