// For an explanation of mnemonics on linux and windows see https://github.com/Kong/insomnia/pull/1221#issuecomment-443543435 & https://docs.microsoft.com/en-us/cpp/windows/defining-mnemonics-access-keys?view=msvc-160#mnemonics-access-keys
// Note: Although this unicode character for the Windows doesn't exist, the the Unicode character U+229E ⊞ SQUARED PLUS is very commonly used for this purpose. For example, Wikipedia uses it as a simulation of the windows logo. Though, Windows itself uses `Windows` or `Win`, so we'll go with `Win` here.
// see: https://en.wikipedia.org/wiki/Windows_key
return'Win';
}
// Note: To avoid using a Microsoft trademark, much Linux documentation refers to the key as "Super". This can confuse some users who still consider it a "Windows key". In KDE Plasma documentation it is called the Meta key even though the X11 "Super" shift bit is used.
100:'This interim response indicates that everything so far is OK and that the client should continue with the request or ignore it if it is already finished.',
101:'This code is sent in response to an Upgrade: request header by the client and indicates the protocol the server is switching to. It was introduced to allow migration to an incompatible protocol version, and it is not in common use.',
201:'The request has succeeded and a new resource has been created as a result. This is typically the response sent after POST requests, or some PUT requests.',
202:'The request has been received but not yet acted upon. It is non-committal, meaning that there is no way in HTTP to later send an asynchronous response indicating the outcome of processing the request. It is intended for cases where another process or server handles the request, or for batch processing.',
203:'This response code means returned meta-information set is not exact set as available from the origin server, but collected from a local or a third party copy. Except this condition, 200 OK response should be preferred instead of this response.',
204:'There is no content to send for this request, but the headers may be useful. The user-agent may update its cached headers for this resource with the new ones.',
205:'This response code is sent after accomplishing request to tell user agent reset document view which sent this request.',
206:'This response code is used because of range header sent by the client to separate download into multiple streams.',
207:'A Multi-Status response conveys information about multiple resources in situations where multiple status codes might be appropriate.',
208:'Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly.',
226:'The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.',
300:'The request has more than one possible responses. User-agent or user should choose one of them. There is no standardized way to choose one of the responses.',
301:'This response code means that URI of requested resource has been changed. Probably, new URI would be given in the response.',
302:'This response code means that URI of requested resource has been changed temporarily. New changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.',
303:'Server sent this response to directing client to get requested resource to another URI with an GET request.',
304:'This is used for caching purposes. It is telling to client that response has not been modified. So, client can continue to use same cached version of response.',
307:'Server sent this response to directing client to get requested resource to another URI with same method that used prior request. This has the same semantic than the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.',
308:'This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.',
400:'This response means that the server could not understand the request due to invalid syntax.',
401:'Authentication is needed to get the requested response. This is similar to 403, but is different in that authentication is possible.',
402:'This response code is reserved for future use. Initial aim for creating this code was using it for digital payment systems, but it is not used currently.',
403:'Client does not have access rights to the content, so the server is rejecting to give proper response.',
404:'Server cannot find requested resource. This response code is probably the most famous one due to how frequently it occurs on the web.',
406:"This response is sent when the web server, after performing server-driven content negotiation, doesn't find any content following the criteria given by the user agent.",
408:'This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome or IE9, use HTTP pre-connection mechanisms to speed up surfing (see bug 881804, which tracks the future implementation of such a mechanism in Firefox). Also, note that some servers merely shut down the connection without sending this message.',
409:'This response is sent when a request conflicts with the current state of the server.',
410:'This response is sent when the requested content has been deleted from the server.',
416:"The range specified by the Range header field in the request can't be fulfilled; it's possible that the range is outside the size of the target URI's data.",
417:"This response code means the expectation indicated by the Expect request header field can't be met by the server.",
418:'Any attempt to brew coffee with a teapot should result in the error code "418 I\'m a teapot". The resulting entity body MAY be short and stout.',
421:'The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.',
426:'The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server MUST send an Upgrade header field in a 426 response to indicate the required protocol(s) (Section 6.7 of [RFC7230]).',
428:"The origin server requires the request to be conditional. Intended to prevent \"the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.\"",
429:'The user has sent too many requests in a given amount of time ("rate limiting").',
431:'The server is unwilling to process the request because its header fields are too large. The request MAY be resubmitted after reducing the size of the request header fields.',
501:'The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are GET and HEAD.',
502:'This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.',
503:'The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This responses should be used for temporary conditions and the Retry-After: HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.',
504:'This error response is given when the server is acting as a gateway and cannot get a response in time.',
505:'The HTTP version used in the request is not supported by the server.',
506:'The server has an internal configuration error: transparent content negotiation for the request results in a circular reference.',
507:'The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.',