11.07.2015 Views

Network Working Group R. Fielding Request for Comments: 2616 ...

Network Working Group R. Fielding Request for Comments: 2616 ...

Network Working Group R. Fielding Request for Comments: 2616 ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

public why the request has not been fulfilled, it SHOULD describe thereason <strong>for</strong> the refusal in the entity. If the server does not wish tomake this in<strong>for</strong>mation available to the client, the status code 404(Not Found) can be used instead.10.4.5 404 Not FoundThe server has not found anything matching the <strong>Request</strong>-URI. Noindication is given of whether the condition is temporary orpermanent. The 410 (Gone) status code SHOULD be used if the serverknows, through some internally configurable mechanism, that an oldresource is permanently unavailable and has no <strong>for</strong>warding address.This status code is commonly used when the server does not wish toreveal exactly why the request has been refused, or when no otherresponse is applicable.10.4.6 405 Method Not AllowedThe method specified in the <strong>Request</strong>-Line is not allowed <strong>for</strong> theresource identified by the <strong>Request</strong>-URI. The response MUST include anAllow header containing a list of valid methods <strong>for</strong> the requestedresource.<strong>Fielding</strong>, et al. Standards Track [Page 66]RFC <strong>2616</strong> HTTP/1.1 June 199910.4.7 406 Not AcceptableThe resource identified by the request is only capable of generatingresponse entities which have content characteristics not acceptableaccording to the accept headers sent in the request.Unless it was a HEAD request, the response SHOULD include an entitycontaining a list of available entity characteristics and location(s)from which the user or user agent can choose the one mostappropriate. The entity <strong>for</strong>mat is specified by the media type givenin the Content-Type header field. Depending upon the <strong>for</strong>mat and thecapabilities of the user agent, selection of the most appropriatechoice MAY be per<strong>for</strong>med automatically. However, this specificationdoes not define any standard <strong>for</strong> such automatic selection.Note: HTTP/1.1 servers are allowed to return responses which arenot acceptable according to the accept headers sent in therequest. In some cases, this may even be preferable to sending a406 response. User agents are encouraged to inspect the headers ofan incoming response to determine if it is acceptable.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!