Coduri de status HTTP pe înțelesul tuturor – part 2

Admin | Personals
17 Dec 2012

eroarehtmlV-am rămas dator cu o continuare științifică a articolului despre codurile de status HTTP custom made. Here it comes 😀

10 – Codul 408 – Request Timeout, care ne spune că “The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.”


11 – Codul 409 – Conflict, care ne spune că “The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response body SHOULD include enough information for the user to recognize the source of the conflict. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required. Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might use the 409 response to indicate that it can’t complete the request. In this case, the response entity would likely contain a list of the differences between the two versions in a format defined by the response Content-Type.”


12 – Codul 413 – Request Entity Too Large, care ne spune că : “The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request. If the condition is temporary, the server SHOULD include a Retry- After header field to indicate that it is temporary and after what time the client MAY try again.”


13 – Codul 414 – Request URL too long, care ne spune că : “The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a URI “black hole” of redirection (e.g., a redirected URL prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URL.”


14 – Codul 416 – Requested Range not Satisfiable, care ne spune că : “A server SHOULD return a response with this status code if a request included a Range request-header field, and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.)When this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource. This response MUST NOT use the multipart/byteranges content- type.”


15 – Codul 417 – Expectation Failed, care ne spune că : “The expectation given in an Expect request-header field could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.”


16 – Codul 422 – Unprocessable Entity, care ne spune că : “The request was well-formed but was unable to be followed due to semantic errors.”


17 – Codul 423 – Locked, care ne spune că : “The resource that is being accessed is locked.”


18 – Codul 426 – Upgrade Required, care ne spune că : “The client should switch to a different protocol such as TLS/1.0”


Tags: , , , , , , , , , ,

One Comment

  1. Suzy says:

    Erorile astea sunt noi, dar interesante. Ar trebui aplicate mai des :))

Leave a Reply

Read more:
Despre hacking stuff

E doar un anunț, nu e o aberație personală : având în vedere ultimele atacuri ale hackerilor asupra Înregistratorului de...