No commit activity in last 3 years
No release in over 3 years
Conclusion, Be using this gem is STRONGLY **deprecated**. Because RFC3986 says userinfo in URI is dangerous. But if you want to open-uri such dangerous uri absolutely, it is preferable to use this gem.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 0
>= 0
>= 0
 Project Readme

Gem Version Build Status Code Climate

DangerousOpenUri

Force open dangerous uri.

Detail

Conclusion, Be using this gem is STRONGLY deprecated. Because RFC3986 says userinfo in URI is dangerous.
So that open-uri will not support it.

But if you want to open-uri such dangerous uri absolutely, it is preferable to use this gem.

SEE: https://www.ruby-forum.com/topic/95983

Installation

Add this line to your application's Gemfile:

gem 'dangerous_open_uri'

And then execute:

$ bundle

Or install it yourself as:

$ gem install dangerous_open_uri

Usage

require 'dangerous_open_uri'

open('http://user:pass@example.co.jp/secret/page').read
#=> Enable to read `http://user:pass@example.co.jp/secret/page` sources

open('http://example.co.jp/index.html', proxy: 'http://user:pass@proxy.example.com')
#=> Proxy basic authentication uses `user` and `pass`

Contributing

  1. Fork it ( https://github.com/[my-github-username]/dangerous_open_uri/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request