Network errors are hits which were not delivered completely from the TCP level view. That is left to the discretion of the server owner. It is not necessary to mark all permanently unavailable resources as "gone", or to keep the mark for any length of time.
Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's site.
The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable, and that the server owners desire that remote links to that resource be removed. This response is cacheable unless indicated otherwise.
#Irip not working code
If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) should be used instead. Clients with link-editing capabilities should delete references to the Request-URI after user approval. This condition is expected to be considered permanent. The requested resource is no longer available at the server, and no forwarding address is known. 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.ĭ.1.11 Failure website-error http-gone (410) For example, if versioning was 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 cannot complete the request. However, that might not be possible, and is not required.Ĭonflicts are most likely to occur in response to a PUT request. Ideally, the response entity would include enough information for the user or user agent to fix the problem. The response body should include enough information for the user to recognize the source of the conflict. 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 request could not be completed due to a conflict with the current state of the resource. User agents are encouraged to inspect the headers of an incoming response to determine if it is acceptable.ĭ.1.10 Failure website-error http-conflict (409) In some cases, this may even be preferable to sending a 406 response. HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept headers sent in the request. However, this specification does not define any standard for such automatic selection. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice may be performed automatically. The entity format is specified by the media type given in the Content-Type header field. Unless it was a HEAD request, the response should include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
D.1.7 Failure website-error http-not-acceptable (406)
0 kommentar(er)
