ruby/rubygems · error · Gem::RemoteFetcher::FetchError

redirecting to non-https resource: #{location}

Error message

redirecting to non-https resource: #{location}

What it means

Error "redirecting to non-https resource: #{location}" thrown in ruby/rubygems.

Source

Thrown at lib/rubygems/remote_fetcher.rb:235

    response   = request uri, fetch_type, last_modified do |req|
      headers.each {|k,v| req.add_field(k,v) }
    end

    case response
    when Gem::Net::HTTPOK, Gem::Net::HTTPNotModified then
      response.uri = uri
      head ? response : response.body
    when Gem::Net::HTTPMovedPermanently, Gem::Net::HTTPFound, Gem::Net::HTTPSeeOther,
         Gem::Net::HTTPTemporaryRedirect then
      raise FetchError.new("too many redirects", uri) if depth > 10

      unless location = response["Location"]
        raise FetchError.new("redirecting but no redirect location was given", uri)
      end
      location = Gem::Uri.new location

      if https?(uri) && !https?(location)
        raise FetchError.new("redirecting to non-https resource: #{location}", uri)
      end

      fetch_http(location, last_modified, head, depth + 1)
    else
      custom_error = response["X-Error-Message"]
      error_detail = custom_error || response.message
      raise FetchError.new("Bad response #{error_detail} #{response.code}", uri)
    end
  end

  alias_method :fetch_https, :fetch_http

  ##
  # Downloads +uri+ and returns it as a String.

  def fetch_path(uri, mtime = nil, head = false)
    uri = Gem::Uri.new uri

View on GitHub (pinned to 86cbb817a3)

Solutions

1. Use an https:// gem source; RubyGems refuses redirects to plain http
2. Update the source URL in your Gemfile/.gemrc to the https endpoint

When it happens

Trigger: Thrown at lib/rubygems/remote_fetcher.rb:235 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of ruby/rubygems@86cbb817a3 (2026-08-23). Data as JSON: /api/errors/8219ad66bdd03020. Report an issue: GitHub.