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