maxmustermann/dotnet-core
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update 3.0.0-preview-known-issues.md

Browse source
This commit is contained in:
Brennan 2019-09-03 13:12:52 -07:00 committed by GitHub
parent c6739cd950
commit d2715eb7cf
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
release-notes/3.0/preview/3.0.0-preview-known-issues.md
View file

@ -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.
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
var builder = new WebHostBuilder()
.UseIIS()
.ConfigureServices(services =>
app.Use(next => context =>
{
if (context.WebSockets.IsWebSocketRequest)
{
services.Configure<IISServerOptions>(options => options.MaxRequestBodySize = long.MaxValue);
});
context.Features.Get<IHttpMaxRequestBodySizeFeature>()?.MaxRequestBodySize = null;
}
return next(context);
});
```
### Preview 8