发表新帖
发表新帖

jquery file upload - IE done callback data.result issue

后端 未结
关注
8 718
借酒劲吻你
借酒劲吻你 2020-12-01 05:41

I\'m using jQuery file upload plugin.

I don\'t use the UI part, only basic one.

When I do the following, I\'m having an issue in

相关标签:
8条回答
  • 野性不改
    2020-12-01 05:48

    I just ran into the same problem, and I think it is due to the fact that XHR file uploads are not supported in IE (even 9). Here's what I believe is happening, and my solution:

    Since Safari 5+, Firefox 4+, and Chrome support XHR file uploads, the fileupload plugin can transfer the files truly asynchronously, allowing for a pure text response from the server. This pure text response is available via data.result in the done event handler, and can be used easily.

    In IE, however, the file transfer occurs via a full page refresh in a hidden iframe, causing data.result in the done handler to be a full document object, with the response text wrapped deep inside <html><body><iframe><pre> tags.

    Not only does this make it a pain to get to the data in IE, it makes the way you get to the data different between browsers.

    My solution:

    I set the forceIframeTransport option to true, which makes all browsers transfer files with a hidden iframe, like IE. It's unfortunate to miss out on XHR file uploads, but this at least gives us the same kind of response in all browsers. Then, in my done handler, I extracted the result from the document object like so:

    var result = $( 'pre', data.result ).text();

    In your case, I think the code would look something like this:

    $('input#fileupload').fileupload({
    forceIframeTransport: true,
    url: '/upload',
    done: function ( e, data ) {
     var result = $( 'pre', data.result ).text();
     if( result != null && $.trim( result ) != '' )
        $( 'a#attachment' ).html( result );
    }
...

    Also important to note here is that the Content Type of the response from my server is 'text/plain'. As you may have noticed, IE sometimes prompts the user to save or open a json response.

    Here are a couple links that proved useful when resolving the problem: https://github.com/blueimp/jQuery-File-Upload/wiki/Browser-support (see 'XMLHttpRequest' section at bottom) https://github.com/blueimp/jQuery-File-Upload/wiki/Options (see 'forceIframeTransport' about 1/3 of the way down)

    Hopefully this helps!

    0 讨论(0)
  • 清酒与你
    2020-12-01 05:50

    The answers here were very useful to understand and solve the problem. I ended up with a satisfactory if hacky solution, that allows modern browsers to upload using XmlHttpRequest, and IE9 to use iframe (didn't test with IE7/8) :

    • Use jquery.iframe-transport.js, it will take care of extracting the response from the iframe. Just include it in the page, the fileupload plugin will use it.
    • On the server action used to upload the files, return a JSON result, but with content-type set to "text/plain", in order to avoid IE prompting the user to open the file
    • In the done callback, manually evalutate the JSON text
    • Finally, use the evaluated result object as before

    Here is the JS code :

    //file upload
var upload = $(fileUploadElmtId).fileupload({

    dataType: 'text',  //if we use JSON IE9 will ask the user to open the file... see the FileUploadController class
    url: uploadUrl,
    autoUpload: true,

    done: function (e, data) {


        //parse the JSON string that was received from the server - since it was received as text/plain it is not automatically evaluated
        var result = $.parseJSON(data.result);

        $.each(result.files, function (index, file) {
            //do something with the result - in my case it is an array of uploaded files...
        }
    }
}
    0 讨论(0)
  • 逝去的感伤
    2020-12-01 05:58

    My problem, the reason is: Cross-Domain.

    That is to say: in IE8/9, your server url should under the same domain as your js file. For jquery.iframe-transport.js is based on iframe, in which you can not cross-domain. Check hehe

    You need not set the forceIframeTransport to true, for jquery.file-upload.js will judge the browser itself.

    Your server should return Content-Type: text/html, or maybe text/plain, and your js could use dataType: 'json', no problem. At least, mine is.

    When you debug, you could set breakpoint in jquery.iframe-transport.js at about line85, the try/catch block. If it can break there, that means iframe used, and you could get the response. At this time, you could see your json in the DOM(in iframe), but if you cross-domained, you would got response as undefined.

    My code. No special:

    $('.input-upload').fileupload({
    url: url, 
    dataType: 'json',
    autoUpload: false,
    acceptFileTypes: /(\.|\/)(gif|jpe?g|png)$/i,
    maxFileSize: 999000,
    previewMaxWidth: 114,
    previewMaxHeight: 70,
    previewThumbnail: false,
    xhrFields: {
        withCredentials: true
    }
}).on('fileuploadadd', function (e, data) {
    $.each(data.files, function (index, file) {
        data.submit().success(function (json, textStatus, jqXHR) {
            // on success
        }).error(function (jqXHR, textStatus, errorThrown) {
            // on error
        });
    });
}).on('fileuploadprocessalways', function (e, data) {
    var _this = this;
    var file = data.files[data.index];
    if (file.preview) {
        // 显示图片预览
        var preview = $(this).parent().siblings('.preview');
        preview.append(file.preview).removeHide();
    }
});
    0 讨论(0)
  • 既然无缘
    2020-12-01 06:02

    I had problems similar to the ones mentioned above and found that changing the response type from application/json to text/plain fixed those issues.

    0 讨论(0)
  • 爱一瞬间的悲伤
    2020-12-01 06:02

    Actually this is what the jquery.iframe-transport.js is for (the basic version also include this plugin as additional reference). What you need is to set the dataType property to json and the jquery.iframe-transport plugin will automatically parse the iframe result, so you can have the same logic in your done handler.

    $('#fileupload').fileupload({
...
    dataType: 'json'
...
});
    0 讨论(0)
  • 名媛妹妹
    2020-12-01 06:08

    Thanks to @Justin for a great explanation on this. I would avoid making queries for the "pre" element and instead make a simple solution like commented by @EnsignRicky

    done: function (e, data) {
  var result = data.result[0].body ? data.result[0].body.innerHTML : data.result
}
    0 讨论(0)
 看不清?
提交回复
热议问题