You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering an issue when trying to push all content from one server to another. I'm getting the following error:
I've configured the following in my Startup.cs thinking it would be sufficient, but I'm not sure if this is the correct approach or if I should have this configuration in a web.config file as mentioned in the guide.
Here's the code I've added:
public class CustomLimitMiddleware : IMiddleware
{
public async Task InvokeAsync(HttpContext context, RequestDelegate next)
{
var httpMaxRequestBodySizeFeature = context.Features.Get<Microsoft.AspNetCore.Http.Features.IHttpMaxRequestBodySizeFeature>();
if (httpMaxRequestBodySizeFeature is { IsReadOnly: false })
{
httpMaxRequestBodySizeFeature.MaxRequestBodySize = 524288000L; //500 MB
}
await next.Invoke(context);
}
}
I am not 100% sure if the middleware stuff will always get hit when using IIS, or indeed if there is an order thing to it (I'm just not up to speed fully with that config). I would try the web.config settings see if that fixes it,
When I add the configuration to the web.config, the servers fail. They look like this, and I see a NotFound error in the call they make. I can access the Back Office without any issues, but I can't perform a synchronization.
Uh oh!
There was an error while loading. Please reload this page.
Hi team,
I'm encountering an issue when trying to push all content from one server to another. I'm getting the following error:
I've configured the following in my Startup.cs thinking it would be sufficient, but I'm not sure if this is the correct approach or if I should have this configuration in a web.config file as mentioned in the guide.
Here's the code I've added:
Could you please let me know if this configuration might be causing the issue, or if it could be something else?
Thanks!
The text was updated successfully, but these errors were encountered: