axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Haszlakiewicz (JIRA)" <>
Subject [jira] Created: (AXIS2C-1474) tcpmon logs corrupted responses in tcpmon_traffic.log
Date Tue, 13 Apr 2010 22:21:50 GMT
tcpmon logs corrupted responses in tcpmon_traffic.log

                 Key: AXIS2C-1474
             Project: Axis2-C
          Issue Type: Bug
    Affects Versions: 1.6.0
            Reporter: Eric Haszlakiewicz

I've been attempting to use tcpmon to diagnose various problems since doing so often requires
looking at exactly what was send and received.  Unfortunately, tcpmon doesn't log the exact
response that is returned.  It appears to be converting any instances of "><" to ">\n<".
Besides just the basic problem of it not being what was actually transferred, this also causes
inconsistency between headers like Content-Length and the actual length of the data, and generally
makes things rather confusing.

Sample testcase, assuming you have the "socket" program installed:
Window #1:
printf "HTTP/1.0 200 OK\r\nContent-Length: 2\r\n\r\n><" > response.txt
printf "cat response.txt" >
chmod +x
socket -s 1234 -v -p   # listen on port 1234 and runs

Window #2:
tcpmon -lp 1235 -tp 1234 -th localhost

Windows #3:

echo foo | telnet localhost 1235

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message