Host should handle client disconnects received in FrontEnd when Functions are executing

[satvu]

Investigative information

Result of CRI. Due to an update in the FrontEnd, the FrontEnd table will log 400.604 errors (client gone, client disconnected), but the host will continue executing the request from that same client despite the client disconnecting during execution. The following pattern is present in the logs, chronologically:

1. FunctionsLogs logs HttpRequestExecuting.
2. FrontEnd logs 400.604 error because the client disconnects.
3. FunctionsLogs eventually logs HttpRequestExecuted shortly after and returns the work done by the Function, ignoring/not knowing about the client disconnect.

Expected behavior

When the host receives client disconnect information it should cancel the request execution (mostly likely using cancellation tokens).

Actual behavior

Host continues execution despite the client disconnect.

[jharbieh-microsoft]

Hi team! Anyone looking at this issue?

[satvu]

@jharbieh-microsoft Are you currently observing this behavior? We will have to re-evaluate this issue as we have made potentially related updates to cancellation handling/flow since the original issue was opened.