Assertion Check HTTP Response Code is not being fired

Document ID : KB000074311
Last Modified Date : 30/03/2018
Show Technical Document Details
Issue:
The flow of a specific Virtual Service should be modified depending on the VSI response HTTP code.
If the HTTP response code is between the 200 range, the next step in the VSM should be a REST step.
The assertion Check HTTP Response Code was added to the VSM in the Responder step and when running the Virtual Service in the ITR, we could see the assertion being evaluated but not fired. Consequently, the REST step was not being executed.
 
Environment:
This behavior was found while working with DevTest on release 8.0.2.
Resolution:
Instead of using the Check HTTP Response Code assertion, use the Ensure Result Contains Expression assertion and under Regular Expression, provide HTTP-Response-Code=2\d\d
Additional Information: