Forum Discussion

NAVTEQ_Support_1's avatar
NAVTEQ_Support_1
Contributor
13 years ago

Mock sending extra characters after header

Hi,

We have defined this response to be delivered by our mock:

<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<getChargePointInfoResponse xmlns="urn://Vas/Cs/2010/12/"></getChargePointInfoResponse>
</s:Body>
</s:Envelope>

And this is what we see as raw response when querying that mock from SoapUI:

HTTP/1.1 200 OK
Content-Type: application/soap+xml;charset=UTF-8
Content-Encoding: gzip
Transfer-Encoding: chunked
Server: Jetty(6.1.x)

<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<getChargePointInfoResponse xmlns="urn://Vas/Cs/2010/12/"></getChargePointInfoResponse>
</s:Body>
</s:Envelope>

So far so good... But our system which was running against that mock was seeing some extra characters there which caused problems so I investigated inside SoapUI with http log and this is what I saw:

Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "POST /mockVasPublisherServiceSoap HTTP/1.1[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "Accept-Encoding: gzip,deflate[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "Content-Type: application/soap+xml;charset=UTF-8;action="/GetChargePointInfo"[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "User-Agent: Jakarta Commons-HttpClient/3.1[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "Host: 127.0.0.1:8088[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "Content-Length: 282[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ns="urn://Vas/Cs/2010/12/">[\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " <soap:Header>[\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " <ns:subscriberIdentity>navteq</ns:subscriberIdentity>[\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " </soap:Header>[\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " <soap:Body>[\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " <ns:getChargePointInfoRequest/>[\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> " </soap:Body>[\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:>> "</soap:Envelope>"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "HTTP/1.1 200 OK[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "HTTP/1.1 200 OK[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "Content-Type: application/soap+xml;charset=UTF-8[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "Content-Encoding: gzip[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "Transfer-Encoding: chunked[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "Server: Jetty(6.1.x)[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "B"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "B"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[0x1f][0x8b][0x8][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x85][0x90]A[0xb][0x82]0[0x18][0x86][0xef]A[0xff]a[0xec][0xae][0xdf]T[0xba][0xc][0xf5][0x90]t[0x8][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[0xa2] [0xba][0xe]]*[0xe8]6[0xfc]V[0xb3] [0x9f][0xd2][0xea]&[0xdd][0xbe][0xf7][0xf0]</[0xef][0x97]"[0xdf][0xa9][0xa7][0xec][0xb4][0x91]d[0xec];[0x85][0x1c]3[0xda]Xk8[0x80]s.tI[0xa8][0x87][0x1a]b[0xc6][0x12]`[0x1b]@-L =@[0xf3][0xf5][0x8a][0x10][0x92]"[0xdf][0xea][0xea][0xe5][0xf1][0x11][0xdb][0x5]A[0x4][0xb7][0xe3][0xe1]R6[0xb2][0x17]A[0xab][0xd0][\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "UJ[0xfa][0xa3][0xaa][0xff][0x94][0xef][0x9b]+ki[0x8b]F[0xc][0xb5]<[0xe9]V[0xd9][0xbd][0xba][0xeb][0xb3]D[0xa3][0x15][0xfa][0x15][0x19]}[0xc]jr][0x5]B[0x81][0x93]'b[0x10][0xc5]@[0xf3][0x14][0x96]Q?[0x7]>{[0xa6]4[0x9f][0xdf][0xef][0xe4]oc[0x1b][0xf4]d*[0x1][0x0][0x0]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "0"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\n]"
Fri Dec 16 12:50:05 CET 2011:DEBUG:<< "[\r][\n]"

Note those two lines with "B" in them, after the header, right before XML code starts. Where are those coming from? I can see that they depend on the actual size of message being sent and is most probably hexadecimal number. So what can we do about this???

Thanks,

roman

5 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hello,

    this is strange - can you perhaps share your project/mock with support (smartbear-sweden-support at smartbear dot com).

    Regards,
    Vladimir
    SmartBear Software
  • SmartBear Support wrote:

    this is strange - can you perhaps share your project/mock with support (smartbear-sweden-support at smartbear dot com).


    done
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi,

    thanks. Issue with id:SOAPUI-3169 opened for tracking.

    Regards,
    Vladimir
    SmartBear Software
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi Roman,

    duh.. actually this is quite alright - it is related to the chunking of the response - the BB is the hex for the size of the coming chunk - surrounded by newline separators..

    Does your client not handle chunked messages correctly!?

    regards!

    /Ole
    SmartBear Software