I have two sites: foo.com and bar.com which dns points to the same ip and whose contents reside on the same folder. The problem is that i purchased a site certificate for only foo.com. If ssl_required redirects a user on bar.com to port 443, then they get an error according to their browser security settings. I have thought of several ways to attack this problem, but would like some advice. (1) hard-code my link_to settings to go to foo.com. This is easy, but ugly, not maintainable (my testing server would no longer work) (2) overload ssl_required to go to foo.com -- might be cleaner, but not sure how to do this (3) set up apache or dns to force ssl traffic over foo.com -- would be most compatible on my ubuntu vps web-server I am really stuck with this and appreciate your advice. Thanks, Tim p.s. this is lower priority, but in general, I am in a rut troubleshooting ssl on my development server since my windows machine and webrick are proving difficult to modify. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Ajit Singh wrote:> I think SSL requires unique IP. I did something like this few years > back.. thats when I found that you can not assign same IP to SSL and > non-sercure website. try using diff IP for non-SSL website. > > I hope it will help > > Ajit > > > On Jul 28, 10:23 pm, Tim Booher <rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>Thanks for your reply, but I don''t think I need a new ip. The problem here is not getting one ip to serve 80 and 443, but forcing the user on bar.com to go to foo.com. I am just trying to do that in the most elegant way. thanks! Tim -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On Tue, 2008-07-29 at 15:42 +0200, Tim Booher wrote:> Ajit Singh wrote: > > I think SSL requires unique IP. I did something like this few years > > back.. thats when I found that you can not assign same IP to SSL and > > non-sercure website. try using diff IP for non-SSL website. > > > > I hope it will help > > > > Ajit > > > > > > On Jul 28, 10:23 pm, Tim Booher <rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> > > Thanks for your reply, but I don''t think I need a new ip. The problem > here is not getting one ip to serve 80 and 443, but forcing the user on > bar.com to go to foo.com. I am just trying to do that in the most > elegant way.---- probably something like this in httpd.conf RedirectPermanent / https://foo.com Craig --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Craig White wrote:> On Tue, 2008-07-29 at 15:42 +0200, Tim Booher wrote: >> > On Jul 28, 10:23 pm, Tim Booher <rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> >> >> Thanks for your reply, but I don''t think I need a new ip. The problem >> here is not getting one ip to serve 80 and 443, but forcing the user on >> bar.com to go to foo.com. I am just trying to do that in the most >> elegant way. > ---- > probably something like this in httpd.conf > > RedirectPermanent / https://foo.com > > CraigSo you think an apache solution is better than a rails solution. If we did a rails solution, what would it be? best, tim -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---