In Avalanche GUI, I know Server Tap & Status Code's location.
In case of same profiles, I can make the 200-OK test case, but can't make the 100-Continue test case.
I saw "Unsuccessful" on the Run Tab..
How can I use it?
This requires a feature request that has not yet been implemented (ref: ER#331086653)
SAPEE may be an alt option depending on the use case.
Per RFC 2616, the 100 Continue Message is meant as a mechanism for the Client and Server to agree that the Client wants to send a request (with an attached body message) to the Server, however, it wants confirmation from the Server that it can accept the body message from the Client. If the Server sends the Client a 100 Continue, it should then continue to read the remaining Client request or respond to the Client with a final Status code.
When setting the Server Transaction Profile to respond with a 100 Continue, the Server sends the 100 Status Code as well as the data specified. The Client eventually closes the TCP Connection with a Reset based on the TCP Timeout value specified within the Clent Network tab (since the Server never closes the Connection). This does not seem to replicate the behavior of the Server as specified within RFC 2616.
I have tried several different test configurations as a work around to this issue and was unsuccessful. Therefore, if you have a customer test case that requires the Continue message with its associated behavior, I would open a SR with Support.
35 People are following this question.
