Issue #10250 has been updated by mame (Yusuke Endoh).

Status changed from Open to Rejected

I think that this is not a bug, but a request for a feature to set HTTP headers for a proxy server instead of endpoint.

My survey:

* golang has a dedicated API, ProxyConnectHeader, to specify HTTP headers for a proxy server: https://github.com/golang/go/issues/13290
* JavaScript's request has a control mechanism to specify which header should be disclosed for a proxy server or not: https://github.com/request/request#proxies

I think ProxyConnectHeader-like feature is good to have, but anyway it should be a new feature rather than a bug fix.  Volunteer is welcome.

----------------------------------------
Bug #10250: User-Agent HTTP header not being set on CONNECT requests
https://bugs.ruby-lang.org/issues/10250#change-82933

* Author: Feldhacker (Chris Feldhacker)
* Status: Rejected
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.0.0p481 (2014-05-08) [i386-mingw32]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
(This was originally reported as RubyGems issue https://github.com/rubygems/rubygems/issues/1012, contributors determined this is actually a bug in core Ruby.)
-----
Per issue https://github.com/rubygems/rubygems/issues/825, RubyGems is supposed to be setting the HTTP User-Agent header, like:
RubyGems/2.2.2 x86_64-darwin-13 Ruby/2.1.0 (2013-12-25 patchlevel 0)

However, network tracing reveals that the User-Agent header is not being sent on HTTP CONNECT requests to the proxy server, which is needed for some companies to be able to white-list RubyGem traffic. Only bare minimal headers are present:

CONNECT api.rubygems.org:443 HTTP/1.1
Host: api.rubygems.org:443

Please set the HTTP User-Agent header on HTTP CONNECT requests.
Thanks!



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

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>