The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. No indication is given of whether the condition is temporary or permanent. The server has not found anything matching the Request-URI. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. Authorization will not help and the request SHOULD NOT be repeated. The server understood the request, but is refusing to fulfill it. HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication". If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information. If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. The response MUST include a The client MAY repeat the request with a suitable Authorization header field (section 14.8). The request requires user authentication.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |