Open zhangqiang-01 opened 4 years ago
I'm not sure why this problem, even if the request and response are problematic, ats should respond correctly.
This issue has been automatically marked as stale because it has not had recent activity. Marking it stale to flag it for further consideration by the community.
Did this happen in an optimized or a debug build? In an optimized build, TSAssert() is optimized out, so TSHttpTxnClientRespGet may have returned TS_ERROR. I don't think ClientRestGet will always return TS_SUCCESS in the close hook unless you are adding the continuation in the SEND_RESPONSE_HDR hook. Have you seen this problem in ATS9?
This issue has been automatically marked as stale because it has not had recent activity. Marking it stale to flag it for further consideration by the community.
@bryancall can i work on this?
One possible cause of this error is that the client response header has already been released or is not available for some reason. To address this issue, you can add a check to ensure that the client response header is available before trying to retrieve it.
Another possible cause of this error is that the TSHttpTxnClose hook is being called after the client response has already been closed. In this case, you may need to move the hook to an earlier point in the transaction flow where the client response header is still available.
When I get ClientRespHeader statistics for response code at TSHttpTxnClose hook, but i find TSHttpTxnClientRespGet return false。
ats version: 7.1.8
Carsh Stack: