-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Configure or disable timeouts on long running requests #46818
Copy link
Copy link
Closed
Labels
area-grpcIncludes: GRPC wire-up, templatesIncludes: GRPC wire-up, templatesarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsarea-signalrIncludes: SignalR clients and serversIncludes: SignalR clients and serversfeature-websocketsIncludes: WebSocketsIncludes: WebSockets
Milestone
Metadata
Metadata
Assignees
Labels
area-grpcIncludes: GRPC wire-up, templatesIncludes: GRPC wire-up, templatesarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsarea-signalrIncludes: SignalR clients and serversIncludes: SignalR clients and serversfeature-websocketsIncludes: WebSocketsIncludes: WebSockets
Type
Fields
Give feedbackNo fields configured for issues without a type.
#46115 adds new request timeout middleware. If a default timeout is configured it could impact long running requests like WebSockets, SignalR, gRPC streaming, etc. These components should consider disabling the timeout for their endpoints, or via the IHttpRequestTimeoutFeature once they transition to long running mode (e.g. after the WebSocket accept).