[ruby-core:65089] [ruby-trunk - Bug #10250] User-Agent HTTP header not being set on CONNECT requests

Issue #10250 has been updated by Usaku NAKAMURA.


I found that the internet-draft (Dec.1995) mentioned about the User-Agent header for CONNECT, but the final RFC (RFC2817, May.2000) doesn't.
Thus, sending the User-Agent header is not official, so I think it's the problem of the proxy server which requires it.

Could you refute me with some concrete evidence?
Enumerating the implementations of proxy servers which need the User-Agent header, showing the specification document or others...

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

* Author: Chris Feldhacker
* Status: Open
* Priority: Normal
* Assignee: 
* Category: 
* 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/