7
 Followers
16
 Likes

SOAP and REST full trace, should book some space for response in case of log truncation.

Integration
New

In case  REST or SOAP has Full logging  and message is BIGG like 10 Mb, than full log trace message will be truncated. It means  we are losing  possibility to see at least response headers and  body start. 


For developer It is very important to see response at least headers, as well usually response is very short and have informative error description inside.  


Here is simple example of trace file (CURRENT SITUATION): 

Request Headers:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000)
Content-Type: text/xml; charset=utf-8
SOAPAction: "sendFile"
Host: 10.10.10.101
Content-Length: 19986843
Request message:
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header></soap:Header><soap:Body><sendFile ><request xmlns=""><document><fileName>filename.jpg</fileName><content>JVBERi0xLjcNJeLjz9MNCjIwMTc1IDAgb2JqDTw8L0xpbmVhcml6ZWQgMS9MIDE0OTg5NDcyL08gMjAxNzkvRSAyMjE0NjUvTiAxMjQvVCAxNDU4NTg1NC9IIFs
.... THOUSAND LINES WITH FILE CONTENT ......
+kftdt0JAaAjm4GNZIOzcUgXeRsRKtvGG3VKzQxu4TjrKoDXmrQRuAWbS5CHbCFRnc7a/nF6mDwVbT5UlKfWByqu2pzUQNU1Yf0gxfQnohTbMVE4TuCpGygkZQnYfyxeo6JOM
<Message truncated in logging because it exceeded the maximum size>

As you see full log is truncated due to maximum size.  

REQUEST: 

Book some space in the trace for Response. like 4..10 KB at least. 

it means that Request message will be truncated,  then I will be added Response Headers and  start of the response body. 


EXPECTED  TRACE To be look like: 
Request Headers:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000)
Content-Type: text/xml; charset=utf-8
SOAPAction: "sendFile"
Host: 10.10.10.101
Content-Length: 19986843
Request message:
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header></soap:Header><soap:Body><sendFile ><request xmlns=""><document><fileName>filename.jpg</fileName><content>JVBERi0xLjcNJeLjz9MNCjIwMTc1IDAgb2JqDTw8L0xpbmVhcml6ZWQgMS9MIDE0OTg5NDcyL08gMjAxNzkvRSAyMjE0NjUvTiAxMjQvVCAxNDU4NTg1NC9IIFs
.... THOUSAND LINES WITH FILE CONTENT ......
+kftdt0JAaAjm4GNZIOzcUgXeRsRKtvGG3VKzQxu4TjrKoDXmrQRuAWbS5CHbCFRnc7a/nF6mDwVbT5UlKfWByqu2pzUQNU1Yf0gxfQnohTbMVE4TuCpGygkZQnYfyxeo6JOM
<Request body truncated in logging because it exceeded the maximum size>


Status Code: OK

Response Headers:
Transfer-Encoding: chunked
Content-Type: text/xml;charset=utf-8
Date: Wed, 09 Sep 2020 09:26:03 GMT
Server: Apache

Response message:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header></SOAP-ENV:Header><SOAP-ENV:Body><ns3:createFileResponse xmlns:ns3=""><request><document><fileName>NewFileAdded000_010</fileName><content>JVBERi0xLjQKMSAwIG9iago8PAovVGl0bGUgKP7/AFYAYQBuAGcAaQBuACAALQAgAFMAZQBsAGYAUwBlAHIAdgBpAGMAZQBSAGUAYwBlAGkAcAB0KQo
.......
<Response body truncated in logging because it exceeded the maximum size>


Created on 11 Sep (2 weeks ago)
Comments (2)

 It is very important.

Changed the category to Integration


views
120
Followers
7