nette/nette — pull request #1190 by drahak (2013-07-31 19:42:06+00:00)
Title: Http Response: enable custom status codes

Although I realize advantages of having list of usable response codes in standard application, I ran into problem with it.

I can't use custom status codes such as 422 (Unprocessable Entity) or 429 (Too Many Requests) which is pretty common (especially in Restful services). Only way how to do it is to make proxy class such as https://github.com/drahak/Restful/blob/master/src/Drahak/Restful/Http/ResponseProxy.php#L46-L57 which is not good.

Since even specification says that HTTP Status codes are extensible (see below) when client understands the class (first digit in status code), my purpose is to allow all codes in interval <100; 599>

http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1.1
```
HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes, though such understanding is obviously desirable. However, applications MUST understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent to the x00 status code of that class, with the exception that an unrecognized response MUST NOT be cached. For example, if an unrecognized status code of 431 is received by the client, it can safely assume that there was something wrong with its request and treat the response as if it had received a 400 status code. In such cases, user agents SHOULD present to the user the entity returned with the response, since that entity is likely to include human- readable information which will explain the unusual status.
```