Bug #859
open-uri doesn't allow redirection to https
| Status: | Assigned | Start date: | 12/12/2008 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | |||
| Target version: | 2.0.0 | |||
| ruby -v: | - |
Description
Only ftp and http are checked in regex in OpenURI.redirectable? method. Please see the attached patch.
Related issues
History
Updated by shyouhei (Shyouhei Urabe) over 3 years ago
- Assignee set to akr (Akira Tanaka)
Updated by romanbsd (Roman Shterenzon) over 3 years ago
Originally reported on: ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-linux]
Updated by romanbsd (Roman Shterenzon) over 3 years ago
I quote from [ruby-core:21234] : But first of all the HTTP --> HTTPS redirection should be still considered ok. Regarding the other way, well, the Referer should be set to the URL that redirected us. I believe this is not currently implemented. As for cookies, AFAIK there's no direct support for cookies in Net::HTTP nor open-uri, so if the programmer wants to use cookies, she has to set it manually via a "Cookie" header. And since no support for cookies as per RFC2109 is in place, no security measures are implemented. So for example one URL can redirect to other (also HTTP) URL, which is in another domain, and the cookie (actually header) will be sent anyway. So the fact that the "secure" attribute of cookie is unsupported diminishes in light of this. Therefor I think that redirecting from HTTPS to HTTP should be considered ok too.
Updated by nobu (Nobuyoshi Nakada) over 2 years ago
Hi, At Tue, 3 Feb 2009 17:53:36 +0900, Roman Shterenzon wrote in [ruby-core:21797]: > I quote from [ruby-core:21234] : > > But first of all the HTTP --> HTTPS redirection should be still considered ok. Then your previous patch is wrong. Index: lib/open-uri.rb =================================================================== --- lib/open-uri.rb (revision 24735) +++ lib/open-uri.rb (working copy) @@ -241,5 +241,5 @@ module OpenURI # However this is ad hoc. It should be extensible/configurable. uri1.scheme.downcase == uri2.scheme.downcase || - (/\A(?:http|ftp)\z/i =~ uri1.scheme && /\A(?:http|ftp)\z/i =~ uri2.scheme) + (/\A(?:http|ftp)\z/i =~ uri1.scheme && /\A(?:https?|ftp)\z/i =~ uri2.scheme) end -- Nobu Nakada
Updated by shyouhei (Shyouhei Urabe) over 2 years ago
- Status changed from Open to Closed
Updated by xaviershay (Xavier Shay) about 1 year ago
Why was this closed? This bug is still present in trunk. A patch was reverted in r21381, but it was not the patch that Nobuyoshi has proposed, and there was no indication as to why it was reverted (my guess is because it allowed https -> http redirection).
Updated by naruse (Yui NARUSE) about 1 year ago
- Status changed from Closed to Assigned
- Priority changed from Low to Normal
Updated by nahi (Hiroshi Nakamura) 11 months ago
- Target version set to 1.9.3
Tanaka-san, please handle this.
Updated by nahi (Hiroshi Nakamura) 10 months ago
Akr, I think we agreed that http -> https redirection is OK. If you don't like ad-hoc change for 1.9.3, I can do that uglish thing instead of you. :) Do you mind if I'd do that?
Updated by akr (Akira Tanaka) 10 months ago
- Target version changed from 1.9.3 to 2.0.0
I'd like generic solution. Especially because open-uri doesn't provide a way to specify headers for each request for redirection.