2 Answers2. Active Oldest Votes. 7. It seems that the web service you’re trying to communicate is behind the xml firewall ( probably IBM DataPower, it does send X-Backside-Transport header on failere) and blocks the error response ( aka. fault message ). This is the default behaviour for the xml firewalls.
Method: ===== POST===== =====REQUEST HEADER===== Array ( [Content-Type] => application/json [Accept] => application/json ) =====RESPONSE HEADER===== Array ( [ X-Backside -Transport] => FAIL FAIL , FAIL FAIL [Connection] => Keep-Alive [Transfer-Encoding] => chunked [X-Content-Type-Options] => nosniff [X-XSS-Protection] => 1 mode=block [Cache-Control].
X-Backside -Transport HTTP Header Common values for this header. FAIL FAIL OK OK OK OK , OK OK Related headers. Connection Content-Type Date Transfer-Encoding Location Server X-Global-Transaction-Id Strict-Transport-Security Www-Authenticate X-Client-Ip Content-Length Keep-Alive Content-Encoding X-Content-Type-Options X-Dp-Watson-Tran-Id X-Powered-By Cache-Control Etag, HTTP/1.1 200 OK X-Backside -Transport: FAIL FAIL Connection: Keep-Alive Transfer-Encoding: chunked Access-Control-Allow-Origin: https://example.com Access-Control-Allow-Credentials: true Access-Control-Allow-Headers:accept, accept-language, content-type, x-ibm-client-id Access-Control-Allow-Methods: methods allowed on the resource Vary: Origin, Please see below, the error message returned when using the Excel Datapool and Test Runner: Response Headers: { X-Backside -Transport= OK OK , #status#=HTTP/1.0 500 Internal Server Error, Connection=close, Content-Type=text/xml} env:Server.
3/10/2021 · HTTP/1.1 200 OK X-Backside -Transport: FAIL FAIL Connection: Keep-Alive Transfer-Encoding: chunked Access-Control-Allow-Origin: http://example/example/testui.html Access-Control-Allow-Credentials: true Access-Control-Allow-Headers:accept, accept-language, content-type, x- ibm -client-id Access-Control-Allow-Method: Vary: Origin, 4/18/2012 · X-Backside -Transport: FAIL FAIL Connection: close Set-Cookie: sticky-key=3460502955.20736.0000 expires=Thu, 24-Nov-2011 15:29:30 GMT path=/ Vary: Accept-Encoding What is causing the FAIL FAIL message ? BTW: A great idea to implement this type of test.
Action.c(13): X-Backside -Transport: FAIL FAIL , FAIL FAIL , FAIL FAIL rn Action.c(13): Connection: Keep-Alivern Action.c(13): Transfer-Encoding: chunkedrn Action.c(13): Content-Type: application/octet-streamrn Action.c(13): WWW-Authenticate: Basic realm=loginrn Action.c(13): Date: Wed, 31 Jul 2013 01:36:44 GMTrn, X-Backside -Transport : FAIL FAIL , FAIL FAIL Cache-Control : no-cache, no-store ,no-cache, no-store, must-revalidate Pragma : no-cache Expires : -1 X-OPNET-Transaction-Trace : a2_52e9775b-b3e0-4ac5-894b-c362bf2952d8-12608-141 X-AspNet-Version : 4.0.30319 X-Powered-By : ASP.NET X-Content-Type-Options : nosniff X-Frame-Options : SAMEORIGIN, DellAssetService – header: ‘ X-Backside -Transport: FAIL FAIL , OK OK ‘ DellAssetService – header: ‘Connection: Keep-Alive’ DellAssetService – header: ‘Transfer-Encoding: chunked’
