With the recent addition of custom domain SSL hosting on Heroku, the possibility of moving some of my production sites over became very real. Very real until I saw the cost of the SSL add-on that is. $1200/ year per site is not really an option.
However, it got a friend and I thinking: Couldn't this be worked around with ProxyPass and ProxyPassReverse? Eg, I run a dedicated VPS that does nothing except act as a proxy server. This server has the SSL certificate on it, and acts as a proxy for https://example.heroku.com Is there anything inherently wrong with this approach? It's kind of what is being done by heroku anyway for their normal hosting (eg everything is behind a proxying server). It's an additional point of failure, and is a potential security risk (in terms of someone hacking into the VPS and redirecting the ProxyPassReverse directive). But with those caveats, is it something that could be done? An example: http://www.example.com acts as a proxy for http://example.heroku.com https://www.example.com acts as a proxy for https://example.heroku.com Any thoughts? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
