 | 1 | initial version |
What does the KO mean.
As @Chuckc's response suggests, it means "not OK". I might suggest that a better string should be chosen, as you shouldn't have had to ask this question; the fact that you did suggests that "KO" is not a particularly obvious choice for that column's value, and should perhaps be reconsidered.
If you agree, please file an issue on the Wireshark issue list.
As the code in @Chuckc's response indicates, a "not OK" response value is one that's either 100 or less, or 400 or more. Section 6 "Response Status Codes" of RFC 7231 "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content" describes the status codes, which are what that code is testing. It indicates that:
Values less than 100 or greater than 599 are not documented there.
So the idea is that codes from 100 to 399 indicate that the request was either successful or hasn't failed yet ("OK"). Requests from 400 up indicate that the request was not successful ("KO").
As for @Chuckc's comment "Not sure why it doesn't include 100 as good response.", 100 is described in section 6.2.1 "100 Continue" as meaning that "the initial part of a request has been received and has not yet been rejected by the server. The server intends to send a final response after the request has been fully received and acted upon." I'm not sure why this is considered "not OK"; perhaps what was intended for "OK" is (i>=100)&&(i<400), meaning "in the range beginning at 100 and ending just before 400.
Chuck, you should probably file an issue on this.
| | 2 | No.2 Revision |
What does the KO mean.
As @Chuckc's response suggests, it means "not OK". I might suggest that a better string should be chosen, as you shouldn't have had to ask this question; the fact that you did suggests that "KO" is not a particularly obvious choice for that column's value, and should perhaps be reconsidered.
If you agree, please file an issue on the Wireshark issue list.
As the code in @Chuckc's response indicates, a "not OK" response value is one that's either 100 or less, or 400 or more. Section 6 "Response Status Codes" of RFC 7231 "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content" describes the status codes, which are what that code is testing. It indicates that:
Values less than 100 or greater than 599 are not documented there.
So the idea is that codes from 100 to 399 indicate that the request was either successful or hasn't failed yet ("OK"). Requests from 400 up indicate that the request was not successful ("KO").
As for @Chuckc's comment "Not sure why it doesn't include 100 as good response.", 100 is described in section 6.2.1 "100 Continue" as meaning that "the initial part of a request has been received and has not yet been rejected by the server. The server intends to send a final response after the request has been fully received and acted upon." I'm not sure why this is considered "not OK"; perhaps what was intended for "OK" is (i>=100)&&(i<400), meaning "in the range beginning at 100 and ending just before 400.
Chuck, you should probably file an issue on this.
UPDATE: I've checked changes into the main and 4.2 branch to 1) treat 100 as OK and 2) report errors as "Error" rather than "KO", so the 4.2.x releases should work that way.
