Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
V2 2.0.5
-
None
Description
A HTTP HEAD method request results in 501 - Not Implemented.
According to OData V2 specification section 2.2.4 HTTP Methods:
...All additional HTTP methods used by this document are specified in [RFC2616]...
and RFC 2616 (refer to newer RFC 7230 and 7231)
in section 7231: Section-4.1
...
All general-purpose servers MUST support the methods GET and HEAD.
All other methods are OPTIONAL.
...
a HEAD request must not lead to a 501 - Not implemented.
--------
-----------------------------------------------------
Method Description Sec. --------
-----------------------------------------------------
GET Transfer a current representation of the target 4.3.1 resource. HEAD Same as GET, but only transfer the status line 4.3.2 and header section. POST Perform resource-specific processing on the 4.3.3 request payload. PUT Replace all current representations of the 4.3.4 target resource with the request payload. DELETE Remove all current representations of the 4.3.5 target resource. CONNECT Establish a tunnel to the server identified by 4.3.6 the target resource. OPTIONS Describe the communication options for the 4.3.7 target resource. TRACE Perform a message loop-back test along the path 4.3.8 to the target resource. --------
-----------------------------------------------------