Feature #8429: Options requests in net/http should be able to accept a response body

• Status: Closed
• Assignee: naruse (Yui NARUSE)
• Target version: 2.2.0

[cpr (Chris Rice)]

As it is currently implemented, Net::HTTP::Options does not allow responses to OPTIONS requests to have a response body:

class Net::HTTP::Options < Net::HTTPRequest
METHOD = 'OPTIONS'
REQUEST_HAS_BODY = false
RESPONSE_HAS_BODY = false
end

According to ((<RFC2616|URL:http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html>)) section 9.2, responses to OPTIONS requests may contain response bodies:

"A 200 response SHOULD include any header fields that indicate optional features implemented by the server and applicable to that resource (e.g., Allow), possibly including extensions not defined by this specification. The response body, if any, SHOULD also include information about the communication options."

As it currently stands, net/http is not useful for issuing an OPTIONS request to an http server which actually makes use of the response body.

[zzak (zzak _)]

• Status changed from Open to Assigned
• Assignee set to naruse (Yui NARUSE)
• Target version set to 2.6

[rubyjoel (Joel Ruby)]

Can we get an update on this? Not sure why it's just sitting here...

[zzak (zzak _)]

• Target version changed from 2.6 to 2.2.0

[naruse (Yui NARUSE)]

• Priority changed from 3 to Normal

http://tools.ietf.org/html/rfc7231#section-4.3.7

[naruse (Yui NARUSE)]

• Status changed from Assigned to Closed
• % Done changed from 0 to 100

Applied in changeset r47078.

---

• lib/net/http/requests.rb (Net::HTTP::Options::RESPONSE_HAS_BODY):
  OPTIONS requests may have response bodies. [Feature #8429]
  http://tools.ietf.org/html/rfc7231#section-4.3.7