Updates

Author: guardrex

aspnetcore/blazor/call-web-api.md

@@ -5,7 +5,7 @@ description: Learn how to call a web API from Blazor apps.
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 03/08/2024
+ms.date: 09/25/2024
 uid: blazor/call-web-api
 ---
 # Call a web API from ASP.NET Core Blazor
@@ -242,6 +242,37 @@ You can address this by flowing prerendered state using the Persistent Component
 
 :::moniker-end
 
+:::moniker range=">= aspnetcore-9.0"
+
+## Client-side request streaming
+
+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 uses [Streams API](https://developer.mozilla.org/docs/Web/API/Streams_API) to permit [request streaming](https://developer.chrome.com/docs/capabilities/web-apis/fetch-streaming-requests).
+
+To enable request streaming, set <xref:Microsoft.AspNetCore.Components.WebAssembly.Http.WebAssemblyHttpRequestMessageExtensions.SetBrowserRequestStreamingEnabled%2A> to `true` on the <xref:System.Net.Http.HttpRequestMessage>.
+
+In the following file upload example:
+
+* `content` is the file's <xref:System.Net.Http.HttpContent>.
+* `/Filesave` is the web API endpoint.
+* `Http` is the <xref:System.Net.Http.HttpClient>.
+
+```csharp
+var request = new HttpRequestMessage(HttpMethod.Post, "/Filesave");
+request.SetBrowserRequestStreamingEnabled(true);
+request.Content = content;
+
+var response = await Http.SendAsync(request);
+```
+
+Streaming requests:
+
+* Require HTTPS protocol and don't work on HTTP/1.x.
+* Include a body but not a `Content-Length` header. [CORS](xref:security/cors) is required, and CORS preflight request is always issued.
+
+For more information on file uploads with an <xref:Microsoft.AspNetCore.Components.Forms.InputFile> component, see <xref:blazor/file-uploads#file-size-read-and-upload-limits> and the example at [Upload files to a server with client-side rendering (CSR)](xref:blazor/file-uploads#upload-files-to-a-server-with-client-side-rendering-csr).
+
+:::moniker-end
+
 ## Add the `HttpClient` service
 
 *The guidance in this section applies to client-side scenarios.*
@@ -257,10 +288,7 @@ In the `Program` file, add an <xref:System.Net.Http.HttpClient> service if it is
 
 ```csharp
 builder.Services.AddScoped(sp => 
-    new HttpClient
-    {
-        BaseAddress = new Uri(builder.HostEnvironment.BaseAddress)
-    });
+    new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) });
 ```
 
 The preceding example sets the base address with `builder.HostEnvironment.BaseAddress` (<xref:Microsoft.AspNetCore.Components.WebAssembly.Hosting.IWebAssemblyHostEnvironment.BaseAddress%2A?displayProperty=nameWithType>), which gets the base address for the app and is typically derived from the `<base>` tag's `href` value in the host page.
@@ -274,10 +302,7 @@ If you're calling an external web API (not in the same URL space as the client a
 
 ```csharp
 builder.Services.AddScoped(sp => 
-    new HttpClient
-    {
-        BaseAddress = new Uri("https://localhost:5001")
-    });
+    new HttpClient { BaseAddress = new Uri("https://localhost:5001") });
 ```
 
 ## JSON helpers
@@ -524,7 +549,7 @@ If you're calling an external web API (not in the same URL space as the client a
 
 ```csharp
 builder.Services.AddHttpClient("WebAPI", client => 
-    client.BaseAddress = new Uri(https://localhost:5001));
+    client.BaseAddress = new Uri("https://localhost:5001"));
 ```
 
 In the following component code:
@@ -624,7 +649,7 @@ If you're calling an external web API (not in the same URL space as the client a
 
 ```csharp
 builder.Services.AddHttpClient<ForecastHttpClient>(client => 
-    client.BaseAddress = new Uri(https://localhost:5001));
+    client.BaseAddress = new Uri("https://localhost:5001"));
 ```
 
 Components inject the typed <xref:System.Net.Http.HttpClient> to call the web API.