-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IE9: Success callback prematurely called on FileAPI.upload.progress #528
Comments
Looking at the shim -- it appears that there's a timeout after 10 seconds at line 126. if I remove this, or change the delay to something larger, things work as expected. Can the 10 second delay be surfaced as a configuration setting? There would also seem to be side effects if FileAPI calls the progress callback multiple times. Thanks, |
There is a check before that timeout |
The service takes some time to process the file, which is why I ran up against this. A configuration setting would be great -- thanks! |
added the option to FileAPI: since version 3.0.0 |
Thank you! |
Sorry to ask, but this doesn't seem to work for me (following the readme : FileAPI = { ... }), and looking at the offending code in the shim, the 10000 value in setTimeout is still hard coded in the 3.0.0 version of your package. Did I miss something ? |
Yeah, I don't think the angular-file-upload release package got properly updated for 3.0.0 -- none of the version numbers have been updated in the files... The demos folder does contain a newer version but outside of that I'm not sure where the 3.0.0 code went. Some checkin bombed or some grunt task failed methinks. See #536 |
Yup, thanks for the update ! Well for now I hard coded another value and it works. |
It was a grunt issue, the name in package.json is now ng-file-upload since angular-file-upload name was already taken in both npm and bower registry so the module is registered there with that name. |
On browsers that use the FileAPI as a fallback, it appears that if the POST exceeds 10 seconds the .success callback is raised, but the data returned is null
If I use fiddler to look at client/server traffic, I don't see a 204, just my file upload, which completes successfully AFTER the .success() method is called in my controller.
FileAPI Debug:
The text was updated successfully, but these errors were encountered: