-
Key: HDATA-34
-
Legacy Issue Number: 17566
-
Status: closed
-
Source: MITRE ( Mr. Jason Mathews)
-
Summary:
Section 6.2.5 states "client MUST NOT use the Max-Forward header when requesting the security mechanisms for a given HDR" but no action is defined for the server.
If Max-Forwards field is truly not permitted on the OPTION operation then recommend adding expected the server action. Suggest to return a 403 Forbidden status code with optional message "Request cannot include Max-Forwards header field".
References:
Max-forwards usage:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.2HTTP status codes
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html -
Reported: Hdata 1.0b1 — Mon, 27 Aug 2012 04:00 GMT
-
Disposition: Resolved — Hdata 1.0
-
Disposition Summary:
Change section 6.2.5 accordingly
-
Updated: Fri, 6 Mar 2015 20:58 GMT
HDATA — Need clarificaton for server response to client request using the Max-Forwards header field
- Key: HDATA-34
- OMG Task Force: hData REST Binding for RLUS 1.0 (hData) FTF