Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Not sure why it doesn't include 100 and 400 as OK or good responses.

Everything outside the range is an error?

epan/dissectors/packet-http.c:

    int i = v->response_code;
...
        if ( (i>100)&&(i<400) ) {
            tick_stat_node(st, "OK", resps_by_this_addr, FALSE);
        } else {
            tick_stat_node(st, "KO", resps_by_this_addr, FALSE);
        }

Not sure why it doesn't include 100 and 400 as OK or good responses.

Everything outside the range is an error?

epan/dissectors/packet-http.c:

    int i = v->response_code;
...
        if ( (i>100)&&(i<400) ) {
            tick_stat_node(st, "OK", resps_by_this_addr, FALSE);
        } else {
            tick_stat_node(st, "KO", resps_by_this_addr, FALSE);
        }

You can compare the counts by looking at the response codes:

http.response.code <101 or http.response.code > 399

Not sure why it doesn't include 100 and 400 as OK or good responses.response.

Everything outside the range is an error?

epan/dissectors/packet-http.c:

    int i = v->response_code;
...
        if ( (i>100)&&(i<400) ) {
            tick_stat_node(st, "OK", resps_by_this_addr, FALSE);
        } else {
            tick_stat_node(st, "KO", resps_by_this_addr, FALSE);
        }

You can compare the counts by looking at the response codes:

http.response.code <101 or http.response.code > 399