#5 repeating content in --print-reply

[Mark Nottingham]

If you specify --print-reply and the response body is large, the headers will print repeatedly as the content streams out.

I think this is because print_reply() is called every time the send_raw_data event fires.

E.g.,

SH0:PUT /test.jpg HTTP/1.1
SH0:Host: www.example.net
SH0:Content-Type: image/jpeg
SH0:Content-Length: 55672
SH0:User-Agent: httperf/0.9.0
SH0:
SS0: header 148 content 55672
SH0:PUT /test.jpg HTTP/1.1
SH0:Host: www.example.net
SH0:Content-Type: image/jpeg
SH0:Content-Length: 55672
SH0:User-Agent: httperf/0.9.0
SH0:
SS0: header 148 content 51476
SH0:PUT /test.jpg HTTP/1.1
SH0:Host: www.example.net
SH0:Content-Type: image/jpeg
SH0:Content-Length: 55672
SH0:User-Agent: httperf/0.9.0
SH0:

...

[Ted Bullock]

Can you attach the results of this defect when executed through callgrind. I am having trouble re-producing this.