PCAP recording does not collect transactions correctly

Document ID : KB000100319
Last Modified Date : 06/06/2018
Show Technical Document Details
Issue:
When a VS recording is done based on a PCAP file only one request is recorded and all responses in the PCAP file are assigned to this request.
Environment:
Devtest 10.2
Cause:
Responses in PCAP dump have neither content-length nor transfer-encoding headers by HTTP 1/1 spec (https://tools.ietf.org/html/rfc7230#section-3.3.3)
for code 200 response end of the message body would be determined when server connection would be closed.

Responses in PCAP dump have Connection: close header, that means that server signals client that it would close the connection after response and all received by client bytes before close would be "the response"

DevTest doesn't operate connections when parsing PCAP dumps, it looks for content-length or transfer-encoding header
That results in "only one request is recorded and all responses in the PCAP file are assigned to this request"
Resolution:
Support might have a patch for the issue. Please open a support case and refer DE363409.