I created a new S3 bucket and tried uploading a file (using Fineuploader 5.0.8) when I was confronted with this error message: "The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256."

I found out that there are currently two ways of creating a signature for an AWS request, v2 and v4. Fineuploader seems to be only supporting the old v2 signatures; this isn't supported by all AWS regions though (e.g. eu-central-1/"EU (Frankfurt)"). See http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html for more details.

As far as I can tell this goes beyond changing the server side code to sign the request; the request itself needs to include an Authorization header that includes the algorithm used for signing ("AWS4-HMAC-SHA256") and other information, and the string to be signed needs to include the algorithm and other information as well, not just the json encoded policy itself.

The current plan is to support simple (non-chunked) uploads to a CloudFront distribution. Chunked uploads are currently not possible when targeting a CloudFront distribution since CloudFront rips off the Authorization header containing the signature before forwarding the request on to S3. The Authorization header is a required field in the request when using any of the S3 multipart upload REST calls, which are needed to support Fine Uploader S3's chunking and auto-resume features. I have opened a request in the CloudFront forums asking for this behavior to be modified so multipart uploads requests can target a CloudFront distribution.

The planned support for this is still mostly undetermined, and it is also not determined if this support will be part of 4.0. Making this part of 4.0 is possible, but looking less likely as I run into issues with CloudFront's handling of upload-related requests. I'm currently struggling to get path patterns for upload requests to work. I've opened another thread in the forum detailing my issue at https://forums.aws.amazon.com/thread.jspa?threadID=137627&tstart=0.

This should be possible once Microsoft adds CORS support to Azure's Blob Storage API. It's unclear at this time what features will be supported when uploading to Azure. The following questions remain until CORS support is added by Microsoft:

• What about non-File-API browsers? Azure will need to support MPE requests via the API. It will also need to be able to allow the response to be redirected to another endpoint, so we can determine if the upload succeeded when uploading from older browsers via iframes.
• What about chunking? Will Azure have a similar solution offered by S3 that allows files to be sent in chunks?

The assumption/hope is that this will be very similar to the direct-to-S3 module (Fine Uploader S3) in concept, though the Azure API will likely differ from the S3 API.

At the last BUILD conference, a promise of CORS support for Blob Storage by the end of the calendar year (2013) was made. This is mentioned on an MSDN blog discussing BUILD as well.

This is blocked until CORS support is added by MS, and until the items mentioned above are clarified.

For resumable uploads where the upload has been divided into chunks, support simultaneously uploading multiple chunks for a single upload at the same time (to increase upload speed)

A good portion of this work was already completed in 4.0, but we may need to do some work to make it much easier for an integrator to allow submitted images to be resized client side and uploaded (possibly along with the original) transparently. I'm not sure offhand what specific improvements are required at this time. We need to discuss further.

Brief description of the changes [REQUIRED]

Adding TypeScript definitions allows integration with TypeScript based projects

What browsers and operating systems have you tested these changes on? [REQUIRED]

N/A

Are all automated tests passing? [REQUIRED]

I haven't written tests for this yet

Is this pull request against develop or some other non-master branch? [REQUIRED]

yes

I make this topic to discuss about the pure-js ans jquery-js version of library.

Supposedly will exists two versions of Fine Uploader:

• 2.x will be pure-js
• 3.x will be jquery-compatible

My opnion is not do that. Will be maintenance be extremally hard and could create inconsistencies between versions. My suggestion is create a pure-js API and a wrapper in jQuery (all will be 3.x version).

For instance:

var up = qq.FileUpload(x);
var up = jQuery.FileUpload(x); // -> call qq.FileUpload(x)

Events, methods and vars need be the same to both.

Files can be:

• fileuploader.js
• jquery-fileuploader.js (requires fileuploader.js)
• prototype-fileuploader.js (requires fileuploader.js) -- for instance

The desvantages will be couldn't use jQuery helpers. But can be create an advanced solution for that in files. For instance:

• fileuploader.js (full version, core + helpers)
• fileuploader-helpers.js (helpers only file, if you don't uses jQuery)
• fileuploader-core.js (core only file)
• jquery-fileuploader.js (requires fileuploader-core.js only)

Or an include once, in build process.

• fileuploader.js (full version, core + helpers version)
• jquery-fileuploader.js (core + jQuery wrapper version)

So you need include only one version.

This is a serious bug that prevents any sort of file uploads in iOS8 Safari. There is no known workaround. Below is the content of the bug report I filed with Apple.

Summary: It seems like there is some issue with access to the files associated with an <input type="file"> element.

A few big issues:

1. FileReader can't seem to read any files associated with a <input type="file">.
2. URL.createObjectURL with a file associated with the element returns an object URL that has no content when loaded.
3. If files are uploaded to a server, even via a simple multipart-encoded form submit, no actual file bytes are sent with the request.

None of these issues occurs in Chrome on iOS8, only Safari.

Steps to Reproduce:

1. Create a simple form with a file input and a submit button
2. Create a simple PHP server that handles file uploads via a multipart encoded POST request.
3. Load the page, select a file, press submit

Expected Results: File is saved to the server.

Actual Results: Either an empty file is saved to the server, or the page loading indicator spins forever after clicking submit due to the lack of file bytes included in the request by Safari.

Version: 8.0 (12A365)

Configuration: iPad

I have created a JSFiddle to demonstrate the issue: http://jsfiddle.net/Q48cw/8/

Normally, uploading a photo will result in a value for 'Bytes uploaded' after the upload. However, for some reason, on iOS when using the following example photo, it stays at zero: http://auto-expire.s3.amazonaws.com/bug/upload.JPG

If you run this script locally and check the server request, the POST data would be empty.

I was using an old AjaxUpload till I figured it out it needs to be upgraded. I just love this nice file/fine uploader. It's so simple to integrate into website.

But it has one strange flaw. When PHP encodes special characters to entities (cos of iFrame limitations) javascript can not decode this response properly.

Because I generate different html code (divs with delete button) for each file upload types, html needs to be perfect. How can I decode this html entities back in javascript or is there another way of doing that?

Thanks!

The current demo page is functional, but not very nice looking. It should probably:

• contain more information/links about the project, such as link to releases page, link to master readme, perhaps an abridged version of the master readme, description of notable features and a summary of Fine Uploader, etc
• contain code samples on the actual page (not a link to the demo js file)
• not look like shit

I've already pulled in twitter-bootstrap css. Perhaps I can make better use of this.

It would be nice if someone could aid in this effort, perhaps someone a bit more skilled than myself in graphic design? Note that I have zero graphic design skills.

After almost 7 years of developing and maintaining this project, I've decided that it's time to archive this (and all other) repositories in the Fine Uploader organization and effectively shut down the project.

I've decided to do this for a number of reasons, here are a few:

1. I no longer have any use for an enterprise-class JS upload library like Fine Uploader in my personal life or in any work projects.
2. I lack the motivation to continue to contribute to this project.
3. I lack the free time at this point in my life to continue to maintain and develop a project of this scale, and the codebase has languished for a little while already.
4. I've grown tired of continuously defending my inactivity and decisions against trolls on Twitter, the issue tracker, and elsewhere. It's draining and I don't have the patience or energy to deal with it any longer. These same people expect to impose their short-sighted and non-generalized values and goals on a project for which they have contributed nothing and are not willing to maintain. The sense of entitlement from a small but vocal minority that do not understand FOSS and refuse to understand it is very much a concern, and I'm simply not interested in shrugging that off anymore.
5. There isn't sufficient momentum behind this project any longer, as such I haven't been able to find the appropriate dedication from the community to not only continue developing this library, but to maintain it going forward.
6. The first incarnation of this codebase is almost 9 years old, and the last major refactor/rewrite was ~5 years ago. That's an eternity in frontend code years. The amount of time required to bring the codebase back up to speed and adjust the mistakes I made years ago as a new frontend developer are simply not possible, due to time and motivation constraints.

I'm going to archive the project shortly, but anyone, of course, is free to fork it and do whatever they please, as this repo will still be available, albeit in read-only mode. I've also locked this issue, as I'm not soliciting input. I've created this for transparency purposes.

For everyone that has helped out on this long journey, I appreciate your efforts, and I hope you understand that it's time for this project to fade off into the sunset. Fine Uploader was my first opportunity to develop something meaningful on the frontend, and I've been able to grow tremendously as a developer as a result. I know Fine Uploader has been an important attribute of many applications, and I'm glad I was able to be a part of that.

Type of issue

• Bug report

Uploader type

• Traditional
• S3

Note: Support requests cannot be accepted due to lack of time.

[Fine Uploader 5.16.2] Caught exception in 'onError' callback - this._uploadData.retrieve(...) is undefined util.js:241:42 qq.log util.js:241:42 log uploader.basic.api.js:304:16 safeCallback uploader.basic.api.js:1964:20 _wrapCallbacks/</self._options.callbacks[callbackName] uploader.basic.api.js:1975:31 _batchError uploader.basic.api.js:502:12 _batchError uploader.api.js:662:12 _onValidateBatchCallbackSuccess uploader.basic.api.js:1684:16 qq.bind/< util.js:691:23 _handleCheckedCallback uploader.basic.api.js:1086:16 _prepareItemsForUpload uploader.basic.api.js:1723:12 _prepareItemsForUpload uploader.api.js:685:12 addFiles uploader.basic.api.js:110:16 processingDroppedFilesComplete uploader.api.js:150:28 uploadDroppedFiles dnd.js:29:8 onDrop/< dnd.js:180:24 then promise.js:32:16 onDrop dnd.js:178:61 attachEvents/< dnd.js:481:16 and therefore any callbacks hang then

Type of issue

• [x] Bug report

Uploader type

• [x] Traditional

    // src is a base64 encoded image
    fetch(src)
      .then(res => res.blob())
      .then(blob => {
        uploader.methods.addFiles([blob]);
        uploader.methods.uploadStoredFiles();
      })

Detailed explanation of the problem

Hi, thanks for this great library! I found one issue when using stopOnFirstInvalidFile and <dialog> elements in Chrome.

Type of issue

• [x] Bug report
• [ ] Feature request

Uploader type

• [x] Traditional
• [ ] S3
• [ ] Azure

const fineUploader = new qq.FineUploader({
    element: element,
    template: templateDomElement,
    // .
    // .
    // .
    validation: {
        stopOnFirstInvalidFile: false,
        allowedExtensions: [
            'jpg', 'jpeg', 'png'
        ]
    },
    // .
    // .
    // .
    //showMessage: message => {
    //    alert(message);
    //}
});

        <div class="qq-total-progress-bar-container-selector qq-total-progress-bar-container">
            <div role="progressbar" aria-valuenow="0" aria-valuemin="0" aria-valuemax="100" class="qq-total-progress-bar-selector qq-progress-bar qq-total-progress-bar"></div>
        </div>

.
.
.
        <dialog class="qq-alert-dialog-selector" style="margin-left:auto; margin-right:auto">
            <div class="qq-dialog-message-selector"></div>
            <div class="qq-dialog-buttons">
                <button type="button" class="qq-cancel-button-selector">@Html.GetResource("Close")</button>
            </div>
        </dialog>

templating.js:1042 Uncaught DOMException: Failed to execute 'showModal' on 'HTMLDialogElement': The element already has an 'open' attribute, and therefore cannot be opened modally.
    at qq.Templating.showDialog (http://localhost:54080/Scripts/libs/fine-uploader/fine-uploader.min.js:6:13421)
    at Object.showMessage (http://localhost:54080/Scripts/libs/fine-uploader/fine-uploader.min.js:5:31111)
    at qq.FineUploader._itemError (http://localhost:54080/Scripts/libs/fine-uploader/fine-uploader.min.js:5:28231)
    at qq.FineUploader._validateFileOrBlobData (http://localhost:54080/Scripts/libs/fine-uploader/fine-uploader.min.js:3:14787)
    at qq.FineUploader._onValidateCallbackSuccess (http://localhost:54080/Scripts/libs/fine-uploader/fine-uploader.min.js:3:11079)
    at Object.onSuccess (http://localhost:54080/Scripts/libs/fine-uploader/fine-uploader.min.js:2:8652)
    at qq.FineUploader._handleCheckedCallback (http://localhost:54080/Scripts/libs/fine-uploader/fine-uploader.min.js:3:1001)
    at http://localhost:54080/Scripts/libs/fine-uploader/fine-uploader.min.js:3:5899

Type of issue

• [ ] Bug report
• [X] Feature request

Uploader type

• [X] Traditional
• [ ] S3
• [ ] Azure

Type of issue

• [ ] Bug report
• [X] Feature request

Uploader type

• [X] Traditional
• [ ] S3
• [ ] Azure