Project

General

Profile

Actions

Bug #10250

closed

User-Agent HTTP header not being set on CONNECT requests

Added by Feldhacker (Chris Feldhacker) over 9 years ago. Updated over 4 years ago.

Status:
Rejected
Assignee:
-
Target version:
-
ruby -v:
ruby 2.0.0p481 (2014-05-08) [i386-mingw32]
[ruby-core:65088]

Description

(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!

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0