Issue #6482 has been updated by naruse (Yui NARUSE).


I'm still considering this, but current thought is

The direction of this seems correct.
On HTTP/1.1 requires Host field in the header.

This is just needed by persistence connection.
When you connect a server and communicate two or more hosts on the server with one connection,
the Host information must be retrieved from each request,
and each response should have its own uri.

This means all request/response should have its own URI information.
So current patch's return the given URI seems not ideal.
----------------------------------------
Feature #6482: Add URI requested to Net::HTTP request and response objects
https://bugs.ruby-lang.org/issues/6482#change-27043

Author: drbrain (Eric Hodel)
Status: Assigned
Priority: Normal
Assignee: naruse (Yui NARUSE)
Category: lib
Target version: 2.0.0


=begin
This patch adds the full URI requested to Net::HTTPRequest and Net::HTTPResponse.

The goal of this is to make it easier to handle Location, Refresh, meta-headers, and URIs in retrieved documents.  (While the HTTP RFC specifies the Location must be an absolute URI, not every server follows the RFC.)  In order to process redirect responses from bad servers or relative URIs in requested documents the user must create an object that contains both the requested URI and the response object to create absolute URIs.  This patch reduces the amount of boilerplate they are required to write.

Only the (({request_uri})) is used from the URI given when creating a request.  The URI is stored internally and updated with the host, port and scheme used to make the request at request time.  The URI is then copied to the response object for use by the user.

To preserve backwards compatibility the new behavior is optional.  This allows requests with invalid URI paths like (({Net::HTTP::Get.new '/f%'})) to continue to work.  Users of string paths will not be able to retrieve the requested URI.

This patch is for support of #5064
=end



-- 
http://bugs.ruby-lang.org/