The request was routed to the listener but the listener did not respond in the required time

[copeworks]

Description

Using this sample https://github.com/Azure/azure-relay/tree/master/samples/hybrid-connections/dotnet/hcreverseproxy to access an on-premise http endpoint that takes more than 60 seconds to respond results in the error "The request was routed to the listener but the listener did not respond in the required time". Despite increasing the operationtimeout calls still timeout after 60 seconds on the client. The call does eventually complete within RequestHandler in HybridConnectionReverseProxy but http client has timed out by this point.

Actual Behavior

1. Http client call to hybrid connection times out after 60 seconds despite increasing the OperationTimeout to 2 minutes via connection string

Expected Behavior

1. Http client call to hybrid connection to not time out after 60 seconds, but timeout after 2 minutes.

[maxwowpow]

@dlstucki any one who can recommend a thing or two for this? I'm very interested too.

[acandylevey]

Facing the same issue here. HttpClient.SendAsync with a custom CancellationToken for 2 minutes fails after 1 minute.