RadAsyncUpload OnClientValidationFailed triggering for no reason

[nico]

I have a RadAsyncUpload and the function for OnClientValidationFailed is getting called with a wrong file size error even though the file is well within the size limit.

Markup

<telerik:RadAsyncUpload runat="server" ID="fUploader" PostbackTriggers="btnSendEmail,btnSaveDraft" OnClientValidationFailed="fileUploadValidationFailed"></telerik:RadAsyncUpload>

server side

fUploader.TargetFolder = uploadPath
fUploader.AllowedFileExtensions = New String() {"*.jpg", "*.png", "*.gif", "*.jpeg", "*.bmp", "*.tiff", "*.pdf", "*.gpx", "*.tcx"}
fUploader.MaxFileSize = 2500000

javascript

function fileUploadValidationFailed(sender, args) {
    var fileExtention = args.get_fileName().substring(args.get_fileName().lastIndexOf('.') + 1, args.get_fileName().length);
    if (args.get_fileName().lastIndexOf('.') != -1) {//this checks if the extension is correct
        if (sender.get_allowedFileExtensions().indexOf(fileExtention.toLowerCase()) == -1) {
            alert("File type selected is not allowed.  Valid file types are .jpg, .png, .gif, .jpeg, .bmp, .tiff, .pdf, .gpx, .tcx");
        }
        else {
            alert("File too large.  Max file size 2 MB.");
        }
    }
    else {
        alert("File type selected is not allowed.  Valid file types are .jpg, .png, .gif, .jpeg, .bmp, .tiff, .pdf, .gpx, .tcx");
    }
}

web.config

<system.web>
    <httpRuntime maxRequestLength="8192"/>

[Allen]

Did you ever resolve this?  I have just started getting the same behavior.  I do see that you have put in the extensions like 

*.jpg, *.png etc.  with wildcard asterisks.  I am not sure those are permitted int he AllowableFileExtensions - should just be .jpg,.png etc. and others have mentioned that spaces between the extensions can be a problem too.... 

[Peter Milchev]

Hello,

The server-side default check for the extension is a below:

foreach (var ext in fUploader.AllowedFileExtensions)
{
    if (fileExtension.ToLower().Trim('.') == ext.ToLower().Trim('.'))
    {
        return true;
    }
}

The fileExtention.ToLower() is something like ".jpg" while the ext.ToLower() will be "*.jpg" so that is the reason the incorrect file extension is expectedly thrown.

As Allen has correctly suggested, the allowed extensions need to be with no spaces and no characters before the dot.

New String() { ".jpg", ".png", ".gif", ".jpeg", ".bmp", ".tiff", ".pdf", ".gpx", ".tcx" }

With that said, the more accurate client-side validation is done by splitting the string to an array:

var allowedExtentions = sender.get_allowedFileExtensions().split(",");

if (args.get_fileName().lastIndexOf('.') != -1) {//this checks if the extension is correct
       if(allowedExtentions.indexOf(fileExtention.toLowerCase()) == -1) {

Regards,
Peter Milchev
Progress Telerik

[Allen]

Typo:  Extentions everywhere needs to be Extensions

 

Fixup (using Linq)

var xt = ".pdf,  .doc,docx,     .xls";  // configurable extensions for particular type(s) of documents in web.config, so these are a mess, need to standardize for RadAsyncUpload.AllowablFileExtensions
var fixedExt = xt.Split(',').Select(x => (x.Trim().StartsWith(".") ? x.Trim() : string.Concat(".", x.Trim())));
//fixedExt.Dump(); // LinqPad https://www.linqpad.net/
//Value
//.xls
//.pdf
//.docx
//.doc