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
Currently Ocelot doesn't allow POST requests with big bodies. Effectively it forbids uploading relatively big files.
"Error Code: UnmappableRequestError Message: Error when parsing incoming request, exception: Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Request body too large.
at Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException.Throw(RequestRejectionReason reason)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1MessageBody.ForContentLength.OnReadStarting()
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.MessageBody.TryInit()
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.MessageBody.CopyToAsync(Stream destination, CancellationToken cancellationToken)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpRequestStream.CopyToAsyncInternal(Stream destination, CancellationToken cancellationToken)
at Ocelot.Request.Mapper.RequestMapper.ToByteArray(Stream stream)
at Ocelot.Request.Mapper.RequestMapper.MapContent(HttpRequest request)
at Ocelot.Request.Mapper.RequestMapper.Map(HttpRequest request) errors found in ResponderMiddleware. Setting error response for request path:/, request method: POST"
This can be worked around on the application level:
But it would be much better if it was possible on request level, preferebely as a part of ReRoute configuration.
Also it's not completely clear if Ocelot manages to resend request with big content. I face another issue:
"Error making http request, exception: System.Net.Http.HttpRequestException: Error while copying content to a stream. ---> System.IO.IOException: Unable to read data from the transport connection: Broken pipe. ---> System.Net.Sockets.SocketException: Broken pipe
--- End of inner exception stack trace ---
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Http.HttpConnection.WriteAsync(ReadOnlyMemory`1 source)
at System.Net.Http.HttpContent.CopyToAsyncCore(ValueTask copyTask)
--- End of inner exception stack trace ---
at System.Net.Http.HttpContent.CopyToAsyncCore(ValueTask copyTask)
at System.Net.Http.HttpConnection.SendRequestContentAsync(HttpRequestMessage request, HttpContentWriteStream stream, CancellationToken cancellationToken)
at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
Though it's not yet clear is the problem is in Ocelot.
The text was updated successfully, but these errors were encountered:
Currently Ocelot doesn't allow POST requests with big bodies. Effectively it forbids uploading relatively big files.
This can be worked around on the application level:
But it would be much better if it was possible on request level, preferebely as a part of ReRoute configuration.
Also it's not completely clear if Ocelot manages to resend request with big content. I face another issue:
Though it's not yet clear is the problem is in Ocelot.
The text was updated successfully, but these errors were encountered: