Forum: Ruby-core [ruby-trunk - Feature #8429][Open] Options requests in net/http should be able to accept a response

9d5d58dc55773bbf77291bd1bf73d78f?d=identicon&s=25 cpr (Chris Rice) (Guest)
on 2013-05-21 05:55
(Received via mailing list)
Issue #8429 has been reported by cpr (Chris Rice).

----------------------------------------
Feature #8429: Options requests in net/http should be able to accept a
response body
https://bugs.ruby-lang.org/issues/8429

Author: cpr (Chris Rice)
Status: Open
Priority: Low
Assignee:
Category: lib
Target version:


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.
7fe945668a4fc098e886e20dea71d2ee?d=identicon&s=25 zzak (Zachary Scott) (Guest)
on 2013-06-02 09:18
(Received via mailing list)
Issue #8429 has been updated by zzak (Zachary Scott).

Status changed from Open to Assigned
Assignee set to naruse (Yui NARUSE)
Target version set to next minor


----------------------------------------
Feature #8429: Options requests in net/http should be able to accept a
response body
https://bugs.ruby-lang.org/issues/8429#change-39635

Author: cpr (Chris Rice)
Status: Assigned
Priority: Low
Assignee: naruse (Yui NARUSE)
Category: lib
Target version: next minor


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.
3bc6a5bb54f807c3f16dcd4a64e528bf?d=identicon&s=25 unknown (Guest)
on 2014-04-21 23:56
(Received via mailing list)
Issue #8429 has been updated by Joel Ruby.


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

----------------------------------------
Feature #8429: Options requests in net/http should be able to accept a
response body
https://bugs.ruby-lang.org/issues/8429#change-46281

* Author: Chris Rice
* Status: Assigned
* Priority: Low
* Assignee: Yui NARUSE
* Category: lib
* Target version: next minor
----------------------------------------
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.
054b5f6b8afdd5f6190bad08e46cd782?d=identicon&s=25 unknown (Guest)
on 2014-04-22 00:19
(Received via mailing list)
Issue #8429 has been updated by Zachary Scott.

Target version changed from next minor to current: 2.2.0

----------------------------------------
Feature #8429: Options requests in net/http should be able to accept a
response body
https://bugs.ruby-lang.org/issues/8429#change-46282

* Author: Chris Rice
* Status: Assigned
* Priority: Low
* Assignee: Yui NARUSE
* Category: lib
* Target version: current: 2.2.0
----------------------------------------
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.
9361878d459f1709feec780518946ee5?d=identicon&s=25 unknown (Guest)
on 2014-08-05 19:47
(Received via mailing list)
Issue #8429 has been updated by Yui NARUSE.

Priority changed from Low to Normal

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

----------------------------------------
Feature #8429: Options requests in net/http should be able to accept a
response body
https://bugs.ruby-lang.org/issues/8429#change-48201

* Author: Chris Rice
* Status: Assigned
* Priority: Normal
* Assignee: Yui NARUSE
* Category: lib
* Target version: current: 2.2.0
----------------------------------------
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.
9361878d459f1709feec780518946ee5?d=identicon&s=25 unknown (Guest)
on 2014-08-05 21:21
(Received via mailing list)
Issue #8429 has been updated by 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

----------------------------------------
Feature #8429: Options requests in net/http should be able to accept a
response body
https://bugs.ruby-lang.org/issues/8429#change-48204

* Author: Chris Rice
* Status: Closed
* Priority: Normal
* Assignee: Yui NARUSE
* Category: lib
* Target version: current: 2.2.0
----------------------------------------
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.
This topic is locked and can not be replied to.