Update 3.0.0-preview-known-issues.md
This commit is contained in:
parent
c6739cd950
commit
d2715eb7cf
|
@ -39,15 +39,17 @@ To update the path for every new terminal session, the `export` entry will need
|
||||||
|
|
||||||
WebSocket connections to IIS In-Process servers will close after the client sends ~30MB of data.
|
WebSocket connections to IIS In-Process servers will close after the client sends ~30MB of data.
|
||||||
|
|
||||||
To workaround this issue you can host your app with the [OutOfProcess](https://docs.microsoft.com/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.0#out-of-process-hosting-model) hosting model. Or you can change the `MaxRequestBodySize` limit in your app during configuration:
|
To workaround this issue you can host your app with the [OutOfProcess](https://docs.microsoft.com/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.0#out-of-process-hosting-model) hosting model. Or you can change the `MaxRequestBodySize` limit in your app when handling WebSocket requests by adding the following to your middleware pipeline:
|
||||||
|
|
||||||
```csharp
|
```csharp
|
||||||
var builder = new WebHostBuilder()
|
app.Use(next => context =>
|
||||||
.UseIIS()
|
{
|
||||||
.ConfigureServices(services =>
|
if (context.WebSockets.IsWebSocketRequest)
|
||||||
{
|
{
|
||||||
services.Configure<IISServerOptions>(options => options.MaxRequestBodySize = long.MaxValue);
|
context.Features.Get<IHttpMaxRequestBodySizeFeature>()?.MaxRequestBodySize = null;
|
||||||
});
|
}
|
||||||
|
return next(context);
|
||||||
|
});
|
||||||
```
|
```
|
||||||
|
|
||||||
### Preview 8
|
### Preview 8
|
||||||
|
|
Loading…
Reference in a new issue