1. Home
  2. Forum
  3. Blazor
  4. .wav not handled when uploading with Blazor File Upload

.wav not handled when uploading with Blazor File Upload

Hi,
Files with characters in the file name fail silently when uploading.  Is there a way to handle this with the component?  It is very common for our clients to have (parenthesis) or spaces in the filenames and the component fails without any error message.  

sample file name 09 - Spanish Harlem Orchestra - Latin Perspective (feat. Joe Locke & Jeremy Bosch).wav

Thanks!

4 Replies
BR Brian April 28, 2020 05:13 AM UTC

As it turns out it wasn't the file name but the component not sending .wav files to the API.  All other files work except for .wav.   I edited the title to reflect the new information

BC Berly Christopher Syncfusion Team April 28, 2020 01:09 PM UTC

Hi Brian, 
  
Greetings from Syncfusion support. 
  
We have checked the reported scenario and unfortunately the reported issue is not occurred at our end. So, we have prepared the sample and taken video demonstration and attached it below. 
  
  
  
  
Please check the above sample and provide the below details that will help us to check and proceed further at our end.  
  
·       Please share the code example or sample  
·       Please ensure whether the issue is reproduced in the above attached sample 
·       Syncfusion product version 
·       If possible, share the uploaded wav extension file.  
·       Have you faced this issue in the wav file extension else any type of extensions with same file size? 
  
Also, while checking the provided screenshot the issue may be caused due to file size of the application got exceeded. We would like to inform you that, by default, server side blazor SignalR maximum message size is 32KB. So, we can’t upload the very large file to server side blazor since it is an asynchronous upload. This is limitation of the server side blazor. Please find the server side blazor SignalR documentation.     
  
  
So, we suggest you to increase the MaximumReceiveMessageSize in Startup.cs file in your applications to get rid of the reported issue.    
  
[Startup.cs]    
  
namespace BlazorApp1   
{   
    public class Startup   
    {   
        public Startup(IConfiguration configuration)   
        {   
            Configuration = configuration;   
        }   
  
        public IConfiguration Configuration { get; }   
  
        // This method gets called by the runtime. Use this method to add services to the container.   
        // For more information on how to configure your application, visit https://go.microsoft.com/fwlink/?LinkID=398940   
        public void ConfigureServices(IServiceCollection services)   
        {   
            services.AddRazorPages();   
            services.AddServerSideBlazor();   
            services.AddSingleton();   
            services.AddSyncfusionBlazor();   
            services.AddSignalR(e =>   
            {   
                e.MaximumReceiveMessageSize = 10240000;   
            });   
        }   

  
Regards, 
Berly B.C 


BR Brian April 28, 2020 04:51 PM UTC

Yes, you are absolutely correct about the maxfile size.  The solution posted did not work, however increasing the maxAllowedContentLength in the .Net Core API controller worked.  Burned by the 30mb limitation once again!  Thanks for helping to resolve.  Created a web.config and added entry below


 <system.webServer>

    <security>

      <requestFiltering>

       

        <requestLimits maxAllowedContentLength="1073741824" />

      requestFiltering>

    security>

  system.webServer>


BC Berly Christopher Syncfusion Team April 29, 2020 06:07 AM UTC

Hi Brian, 

We are glad to know that your issue is resolved. Please let us know if you need further assistance on this. 
  

Regards, 
Berly B.C 


Loader.
Up arrow icon