HTTP STATUS CODES IN .JSON parsed from https://github.com/waldemarnt/http-status-codes . forked text a little, I added prepended extras on descriptions of 301+302 for myself.

http-status-codes.json

{
    "100" : {
        "title": "Continue",
        "description": "Client should continue with request."
    },
    "101" : {
        "title": "Switching Protocols",
        "description": "Server is switching protocols."
    },
    "102" : {
        "title": "Processing",
        "description": "Server has received and is processing the request."
    },
    "103" : {
        "title": "Processing",
        "description": "Server has received and is processing the request."
    },
    "122" : {
        "title": "Request-uri too long",
        "description": "URI is longer than a maximum of 2083 characters."
    },
    "200" : {
        "title": "Ok",
        "description": "The request was fulfilled."
    },
    "201" : {
        "title": "Created",
        "description": "Following a POST command, this indicates success, but the textual part of the response line indicates the URI by which the newly created document should be known."
    },
    "202" : {
        "title": "Accepted",
        "description": "The request has been accepted for processing, but the processing has not been completed. The request may or may not eventually be acted upon, as it may be disallowed when processing actually takes place. there is no facility for status returns from asynchronous operations such as this."
    },
    "203" : {
        "title": "Partial Information",
        "description": "When received in the response to a GET command, this indicates that the returned metainformation is not a definitive set of the object from a server with a copy of the object, but is from a private overlaid web. This may include annotation information about the object, for example."
    },
    "204" : {
        "title": "No Response",
        "description": "Server has received the request but there is no information to send back, and the client should stay in the same document view. This is mainly to allow input for scripts without changing the document at the same time."
    },
    "205" : {
        "title": "Reset Content",
        "description": "Request processed, no content returned, reset document view."
    },
    "206" : {
        "title": "Partial Content",
        "description": "partial resource return due to request header."
    },
    "207" : {
        "title": "Multi-Status",
        "description": "XML, can contain multiple separate responses."
    },
    "208" : {
        "title": "Already Reported",
        "description": "results previously returned."
    },
    "226" : {
        "title": "Im Used",
        "description": "request fulfilled, reponse is instance-manipulations."
    },
    "301" : {
        "title": "Moved",
        "description": "Permanently moved. The data requested has been assigned a new URI, the change is permanent. (N.B. this is an optimisation, which must, pragmatically, be included in this definition. Browsers with link editing capabiliy should automatically relink to the new reference, where possible)"
    },
    "302" : {
        "title": "Found",
        "description": "Temporarily moved. The data requested actually resides under a different URL, however, the redirection may be altered on occasion (when making links to these kinds of document, the browser should default to using the Udi of the redirection document, but have the option of linking to the final document) as for Forward."
    },
    "303" : {
        "title": "Method",
        "description": "Like the found response, this suggests that the client go try another network address. In this case, a different method may be used too, rather than GET."
    },
    "304" : {
        "title": "Not Modified",
        "description": "If the client has done a conditional GET and access is allowed, but the document has not been modified since the date and time specified in If-Modified-Since field, the server responds with a 304 status code and does not send the document body to the client."
    },
    "305" : {
        "title": "Use Proxy",
        "description": "Content located elsewhere, retrieve from there."
    },
    "306" : {
        "title": "Switch Proxy",
        "description": "Subsequent requests should use the specified proxy."
    },
    "307" : {
        "title": "Temporary Redirect",
        "description": "Connect again to different URI as provided."
    },
    "308" : {
        "title": "Permanent Redirect",
        "description": "Connect again to a different URI using the same method."
    },
    "400" : {
        "title": "Bad Request",
        "description": "The request had bad syntax or was inherently impossible to be satisfied."
    },
    "401" : {
        "title": "Unauthorized",
        "description": "The parameter to this message gives a specification of authorization schemes which are acceptable. The client should retry the request with a suitable Authorization header."
    },
    "402" : {
        "title": "Payment Required",
        "description": "The parameter to this message gives a specification of charging schemes acceptable. The client may retry the request with a suitable ChargeTo header."
    },
    "403" : {
        "title": "Forbidden",
        "description": "The request is for something forbidden. Authorization will not help."
    },
    "404" : {
        "title": "Not Found",
        "description": "The server has not found anything matching the URI given."
    },
    "405" : {
        "title": "Method Not Allowed",
        "description": "Request method not supported by that resource."
    },
    "406" : {
        "title": "Not Acceptable",
        "description": "Content not acceptable according to the Accept headers."
    },
    "407" : {
        "title": "Proxy Authentication Required",
        "description": "Client must first authenticate itself with the proxy."
    },
    "408" : {
        "title": "Request Timeout",
        "description": "Server timed out waiting for the request."
    },
    "409" : {
        "title": "Conflict",
        "description": "Request could not be processed because of conflict."
    },
    "410" : {
        "title": "Gone",
        "description": "Resource is no longer available and will not be available again."
    },
    "411" : {
        "title": "Length Required",
        "description": "Request did not specify the length of its content."
    },
    "412" : {
        "title": "Precondition Failed",
        "description": "Server does not meet request preconditions."
    },
    "413" : {
        "title": "Request Entity Too Large",
        "description": "Request is larger than the server is willing or able to process."
    },
    "414" : {
        "title": "Request URI Too Large",
        "description": "URI provided was too long for the server to process."
    },
    "415" : {
        "title": "Unsupported Media Type",
        "description": "Server does not support media type."
    },
    "416" : {
        "title": "Requested Rage Not Satisfiable",
        "description": "Client has asked for unprovidable portion of the file."
    },
    "417" : {
        "title": "Expectation Failed",
        "description": "Server cannot meet requirements of Expect request-header field."
    },
    "418" : {
        "title": "I'm a teapot",
        "description": "I'm a teapot."
    },
    "420" : {
        "title": "Enhance Your Calm",
        "description": "Twitter rate limiting."
    },
    "421" : {
        "title": "Misdirected Request",
        "description": "Server is not able to produce a response."
    },
    "422" : {
        "title": "Unprocessable Entity",
        "description": "Request unable to be followed due to semantic errors."
    },
    "423" : {
        "title": "Locked",
        "description": "Resource that is being accessed is locked."
    },
    "424" : {
        "title": "Failed Dependency",
        "description": "Request failed due to failure of a previous request."
    },
    "426" : {
        "title": "Upgrade Required",
        "description": "Client should switch to a different protocol."
    },
    "428" : {
        "title": "Precondition Required",
        "description": "Origin server requires the request to be conditional."
    },
    "429" : {
        "title": "Too Many Requests",
        "description": "User has sent too many requests in a given amount of time."
    },
    "431" : {
        "title": "Request Header Fields Too Large",
        "description": "Server is unwilling to process the request."
    },
    "444" : {
        "title": "No Response",
        "description": "Server returns no information and closes the connection."
    },
    "449" : {
        "title": "Retry With",
        "description": "Request should be retried after performing action."
    },
    "450" : {
        "title": "Blocked By Windows Parental Controls",
        "description": "Windows Parental Controls blocking access to webpage."
    },
    "451" : {
        "title": "Wrong Exchange Server",
        "description": "The server cannot reach the client's mailbox."
    },
    "499" : {
        "title": "Client Closed Request",
        "description": "Connection closed by client while HTTP server is processing."
    },
    "500" : {
        "title": "Internal Error",
        "description": "The server encountered an unexpected condition which prevented it from fulfilling the request."
    },
    "501" : {
        "title": "Not Implemented",
        "description": "The server does not support the facility required."
    },
    "502" : {
        "title": "Service temporarily overloaded",
        "description": "The server cannot process the request due to a high load (whether HTTP servicing or other requests). The implication is that this is a temporary condition which maybe alleviated at other times."
    },
    "503" : {
        "title": "Gateway timeout",
        "description": "This is equivalent to Internal Error 500, but in the case of a server which is in turn accessing some other service, this indicates that the respose from the other service did not return within a time that the gateway was prepared to wait. As from the point of view of the clientand the HTTP transaction the other service is hidden within the server, this maybe treated identically to Internal error 500, but has more diagnostic value."
    },
    "504" : {
        "title": "Gateway Timeout",
        "description": "Gateway did not receive response from upstream server."
    },
    "505" : {
        "title": "Http Version Not Supported",
        "description": "Server does not support the HTTP protocol version."
    },
    "506" : {
        "title": "Variant Also Negotiates",
        "description": "Content negotiation for the request results in a circular reference."
    },
    "507" : {
        "title": "Insufficient Storage",
        "description": "Server is unable to store the representation."
    },
    "508" : {
        "title": "Loop Detected",
        "description": "Server detected an infinite loop while processing the request."
    },
    "509" : {
        "title": "Bandwidth Limit Exceeded",
        "description": "Bandwidth limit exceeded."
    },
    "510" : {
        "title": "Not Extended",
        "description": "Further extensions to the request are required."
    },
    "511" : {
        "title": "Network Authentication Required",
        "description": "Client needs to authenticate to gain network access."
    },
    "598" : {
        "title": "Network Read Timeout Error",
        "description": "Network read timeout behind the proxy."
    },
    "599" : {
        "title": "Network Connect Timeout Error",
        "description": "Network connect timeout behind the proxy."
    }
}