Support for GET
Section 6.2.1 of the read-only spec says "shall support the use of the HTTP GET method defined in [RFC2616];" -- Did you mean the definition of GET specifically in section 9.3 of RFC 2616? If so, is the thing you are trying to mandate the use of conditional and partial GET? I think what this bullet is trying to mandate is that the resource server actually be a REST API, but the bullet as written sent me running off trying to read the entire spec to understand the requirement.
Could you simply say that the resource server "shall support the use of HTTP methods defined in section 9 of [RFC2616]? Or did you really need to require that every single resource server out there MUST under all circumstances support a GET method?
Comments (12)
-
-
Clarify that GET is the minimum.
-
- changed status to open
-
I still feel that nothing needs to be changed. However, if clarification is required, we may want to reference https://tools.ietf.org/html/rfc7231#section-4.3.1 as Suhas said. It really is only about letting implementors that GET needs to be supported.
-
I see this as being fixed. It should probably be closed
-
Issue
#84was marked as a duplicate of this issue. -
- changed status to resolved
This has been fixed. RFC 7231 is now being referenced
-
- changed component to Part 1: Baseline
-
- changed component to FAPI 1 - Part 1: Baseline
-
- changed component to FAPI 1 – Part 1: Baseline
-
- changed component to FAPI 1 – Baseline
-
- changed component to FAPI 1: Baseline
- Log in to comment
Isn't RFC 2616 obsoleted by 7230, 7231, 7232, 7233, 7234 and 7235
If we are specifically after the conditional requests then they are defined in 7232. If we are after just the HTTP method definitions then they are defined in 7231