Skip to content

Commit cbae03c

Browse files
committed
Updates
1 parent 7c3a54e commit cbae03c

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

aspnetcore/blazor/file-uploads.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -103,8 +103,6 @@ If you're using the [Autofac Inversion of Control (IoC) container](https://autof
103103

104104
:::moniker range=">= aspnetcore-9.0"
105105

106-
Server-side or client-side, there's no file read or upload size limit for the <xref:Microsoft.AspNetCore.Components.Forms.InputFile> component.
107-
108106
For Chromium-based browsers (for example, Google Chrome and Microsoft Edge) using the HTTP/2 protocol, HTTPS, and [CORS](xref:security/cors), client-side Blazor supports using the [Streams API](https://developer.mozilla.org/docs/Web/API/Streams_API) to permit uploading large files (over 250 MB or larger than the device's available memory) with [request streaming](xref:blazor/call-web-api#client-side-request-streaming).
109107

110108
For non-Chromium browsers, without HTTP/2 protocol, or without HTTPS, client-side Blazor reads the file's bytes into a single JavaScript array buffer when marshaling the data from JavaScript to C#, which is limited to 2 GB or to the device's available memory. Large file uploads, typically 250 MB or larger, may fail for client-side uploads using the <xref:Microsoft.AspNetCore.Components.Forms.InputFile> component.

0 commit comments

Comments
 (0)