added in svn://svn.zabbix.com/branches/dev/ZBXNEXT-2056

Resolving HTTP response codes might be also another use case for ZBXNEXT-1812. This would even allow to resolve to proper messages, when the item value just includes the status code - like it is for instance often the case in log messages.

I'm not saying a value map as requested here is not reasonable. Just want to raise a little bit attention to ZBXNEXT-1812 as I consider it distantly connected

(1) There are two value mappings for 308 status code:

ROW   |110      |17        |308  |Permanent Redirect                  |
ROW   |111      |17        |308  |Resume Incomplete                   | 

<richlv> ouch, sorry about that. resolved in r54463 by adding both values, separated with a slash. RESOLVED

glebs.ivanovskis Good! CLOSED

(2) The list is probably taken from the linked Wikipedia article, but official names for some of the codes seem to be different. For instance, Wikipedia lists "Request Entity Too Large" for 413, but http://tools.ietf.org/html/rfc7231#section-6.5.11 has "Payload Too Large" instead. See also http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml .

<richlv> looks like "Payload" is a more recent version. updated wikipedia page accordingly & changed in r54463
other differences :

• wikipedia page says "Request-URI Too Long" for 414, but http://tools.ietf.org/html/rfc7231#section-6.5.12 says "URI Too Long". keeping wikipedia version for now, asked about this on the talk page
• wikipedia page says "Requested Range Not Satisfiable" for 416, but http://tools.ietf.org/html/rfc7233#section-4.4 says "Range Not Satisfiable". keeping wikipedia version for now, asked about this on the talk page

RESOLVED

glebs.ivanovskis Messages can be perfected later, but now... CLOSED

asaveljevs Regarding 414 and 416, this spelling seems to be used in Apache 2.4.16, Nginx 1.8.0, lighttpd 1.4.37, and Apache Tomcat 8.0.26, although it remains to be investigated where their spelling comes from.

(3) somehow, weirdly, code 500 was missing. added in r54463.

glebs.ivanovskis Very good! CLOSED

Very nice to see this is getting some love for the 3.0 release. Thanks guys!

(4) unofficial code 522 has been added to wikipedia - do we want to include it ? https://en.wikipedia.org/w/index.php?title=List_of_HTTP_status_codes&type=revision&diff=673469015&oldid=672261712

Origin Connection Time-out
This status code is not specified in any RFCs, but is used by CloudFlare's reverse proxies to signal that a server connection timed out.

glebs.ivanovskis Since initial request was to add "most common" codes, I think we can live without 522 for some time and let it mature... or vanish. CLOSED

Available in pre-3.0.0alpha3 (trunk) r55564.

(5) listed in https://www.zabbix.com/documentation/3.0/manual/introduction/whatsnew300#value_map_changes

asaveljevs CLOSED

(6) There are two value mappings to 420 status code:

ROW   |131      |17        |420  |Method Failure                      |
ROW   |132      |17        |420  |Enhance Your Calm                   |

asaveljevs The following are also duplicates:

ROW   |145      |17        |451  |Unavailable For Legal Reasons       |
ROW   |146      |17        |451  |Redirect                            |
...
ROW   |152      |17        |499  |Client Closed Request               |
ROW   |153      |17        |499  |Token required                      |

<richlv> should be finally dealt with in r55579, RESOLVED

asaveljevs Looks good. CLOSED.

(7) standard capitalisation used in r55581 as per https://www.zabbix.org/wiki/Docs/specs/syntax#Syntax

asaveljevs CLOSED

duplicate entries fixed and standard capitalisation used in trunk r55601.

it should be noted that the chosen separator for multiple potential response values, slash, is also present in some of the values themselves. for example, "Token Expired/Invalid" is a single value, but "Client Closed Request/Token Required" are two different values. at this time it has been decided to leave it as is.

The need for HTTP status codes like 404.17 is mentioned at ZBX-9940.