Turns out that the IP of a much-needed new website is blocked from inside our organization's network for reasons that will take weeks to fix. In the meantime, could we set up a reverse proxy on an Internet-based server which will forward SSL traffic and perhaps client IPs to the external site? Load will be light. No need to terminate SSL on the proxy. We may be able to poison DNS so original URL can work.

How do I learn if I need URL rewriting? Squid/apache/nginx/something else? Setup would be fastest on Win 2000, but other OSes are OK if that would help. Simple and quick are good since it's a temporary solution.

Thanks for your thoughts!

link|improve this question

57% accept rate
feedback

2 Answers

Easiest reverse proxy solution for you will probably be IIS 7 with Application Request Routing. It's a very quick install so even if it's not what you're looking for, at least you can give it a shot without spending a whole lot of time.

http://learn.iis.net/page.aspx/489/using-the-application-request-routing-module/

http://www.hanselman.com/blog/NewModulesForIIS7ApplicationRequestRoutingProxyAndLoadBalancingModule.aspx

link|improve this answer
Thanks for the tip. Unless it's changed since blogs.iis.net/wonyoo/archive/2008/07/10/… ARR can't do the "CONNECT tunneling" that's needed to avoid terminating SSL at the proxy. Is there a workaround? – Paul Aug 10 '10 at 23:57
feedback

I use Squid on Window 2003 from http://squid.acmeconsulting.it/ It works very well for as a normal web proxy.

If you think Squid might work, they also have an SSL binary of Squid 2.7 (stable-8) that is "for reverse proxy only - EXPERIMENTAL"

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.