Yes you can!
${httpRouting.reasonCode} | Returns one of the following reason codes when the HTTP routing fails: - -1 (Host Not Found): The Server referenced in the URL (for example, nonexistentServer.l7tech.com) cannot be reached. This code can be returned if either the host does not exist or the host is simply down.
- -2 (Bad URL): The URL is incorrect. This could be caused by an incorrect character such as "#".
- -3 (Connection timeout): An initial message was sent to the URL but no response was received before the connection timeout expired. The connection timeout value is defined in the assertion properties.
- -4 (Read timeout): One of packets being received from the URL took longer than the read timeout value to be received. The read timeout value is defined in the assertion properties.
- -5 (Undefined): An unknown type of error has occurred.
- If successful, will return a valid HTTP Response Code
|
Also note that the context variable ${audit.details.last.fullText} will also display the last audit detail, and in the case of policy failures, it will usually show you the audit record of the failure.