Project

General

Profile

Actions

Feature #8429

closed

Options requests in net/http should be able to accept a response body

Added by cpr (Chris Rice) over 9 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Target version:
[ruby-core:55093]

Description

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.

Actions

Also available in: Atom PDF