SWFUpload

Yes, I have checked the limits. All limits are set to 80 MBs. For references, the SWFUpload limit is set to 40MBs and the file I am uploading is 23 MBs. Also, the upload succesfully completes. If the file limits were too low, the file upload would not complete. The problem is that after the upload is done, the whole system hangs and eventually comes back with a 500 error.

Additionally, this problem is also found on the official demo site which suggests that the error does not lie on the server side.

Any help would be greatly appreciated.

Cheers,
Tim

You haven't provided enough information here. That makes it hard to give very much help.

I've tested SWFUpload with files up to 2GB (the max allowed by IIS).

What version is everything? Flash, Browser, OS, SWFUpload, Server?
What tech are you using? Java, PHP, ASP.Net, Apache, IIS?

You never answered whether a regular everyday HTML upload form works with the same file (targeted at your swfupload upload script).

Have you tried capturing the packets between the client and server to see if the server is returning any additional data with the 500 error? (Flash does not return any data unless an HTTP status of 200 is returned. You must use some other tool to capture this information. I like WireShark.).

The demo site only allows uploads up to 7MB (I know the page says 100MB). This has 2 reasons. 1) I don't have control over the server and can't increase the maximum allowed upload size and 2) it demonstrates what happens when your SWFupload settings and server settings don't match. The upload.php file handles the error by returning a 500 status. If the demo were using the Flash 9 version I could return a 200 status and in the "server data" of uploadSuccess I could report that the file was rejected with some detailed text. The Flash 8 version only understands HTTP status codes so I return 500 to indicate an error.

>>I've tested SWFUpload with files up to 2GB (the max allowed by IIS).
>Was this a local test or a test versus a public server? I believe this is a timing issue rather than a size issue.

These tests are to local servers (not localhost but servers within our LAN). It may very well be a timing issue.

>>You never answered whether a regular everyday HTML upload form works with the same file (targeted at your swfupload upload script).
>I believe I did, but yes, a regular upload works just fine.

Sorry, I must have missed it (or more likely misunderstood)

>>Have you tried capturing the packets between the client and server to see if the server is returning any additional data with the 500 error? (Flash does not return any data unless an HTTP status of 200 is returned. You must use some other tool to capture this information. I like WireShark.).
>I have not, anything in particular you are looking for? It would probably be a lot simpler if you could manage to recreate it against this server as well, but I will do what I can...

Usually more error details are included with the 500 response but Flash (and therefore SWFUpload) ignores the response content and cannot display it to you. A packet capture can help discover this information and can help determine other issues. Packet capture can be daunting but WireShark is pretty good and will even parse the conversion out into an easy to read text-only display.

-------

The 500 error you get on the demo site is probably not related to the 500 error you are getting on your server. The demo site is limited to 7MB uploads (regardless of what the page says or SWFupload allows). Uploading any file over 7MB to the demo site will result in an error. The different demos respond differently depending on how the upload.php script for the demo handles it and what the JavaScript handlers are set to do.

-------

If you have a test site that we can take a look at I'd be happy to give it a go.

-------

There is a known issue where long running processing in the upload script (where you don't return any data for more than 30 seconds) causes Flash to give up and terminate the connection. But I've never seen this result in a HTTP 500 status code. I don't think this is your issue but it's another timing thing to be aware of.

Hello,

I am experiencing same error:
- using 2.1.0 beta
- using multiinstance demo
- production/dev servers
- using upload.php from samples/php
- using f8/f9 same result

Also:
- using sample HTML form from samples/php all works perfectly with same file been uploaded.

Btw, problem appears for ANY file size. Not just for big files...

This is a known issue. There seems to be some debate over whether the Flash Player is following the standard or not. I don't know.

Regardless, mod_security believes Flash Player is not following the standard and so rejects the request.

The only work-around (until Flash Player is fixed) is to disable mod_security.

This site describes disabling mod_security for a specific URL

I got the OK just now from the customer to go ahead and upgrade to the most recent version of the uploader. Hopefully then this will fix the problem, and if not, we'll have a more standard base to go from. Thanks for all your time, I'll let you know how it goes!