fix erroneous catching of protocol violation errors
When an API (wrongly) return a response body and a "204 No content" return code, a "500 protocol violation error" should be raised by APIM instance.
In fact it is the case, but the protocol violation error is raised as a response on the call folowing the erroneous "204" API, not the erroneous API itself. The error is raised only the following call (whatever API it is) that is implemented on the same backend of the "204" API AND if the folowing call is made in the same HTTP session (I mean during the http "keep alive" timeout).
This bug was confirmed by a support request but support team advised me to open an improvement subject since nothing could be do to corrrect the problem (the bug seems to be du to an embedded component of APIM).
Let me know if SR number would help.
Thank you for the feedback! We added this suggestion to the backlog and will update the item when we prioritize it for implementation.