I've done this is nginx, you can have a system where its like http://commonproxy.wikilabs.org/192.168.0.1/ and it would do a proxypass to the ip address in the field over a predefined port, or you could do /192.168.0.1/<port>/
On Tue, Oct 2, 2012 at 7:02 AM, Platonides <[email protected]> wrote: > On 28/09/12 07:12, Ryan Lane wrote: > >> This is on the roadmap for October-December (not sure if it's going to > get > >> pushed back or not), a rough detail of what we need is @ > >> > https://www.mediawiki.org/wiki/Wikimedia_Labs/Reverse_proxy_for_web_services > . > >> Feel free to contribute ideas there. > >> > >> I agree this is something we really need to start working on; however it > >> needs to be done right, so we don't suffer longer term. > >> > > > > Yep. The hard part about this is that even with host headers is that > > we don't know which backends to send requests to. We need a load > > balancer service that acts as a reverse proxy. Of course, we don't > > really want to write this ourselves. Thankfully, there's a proof of > > concept openstack service for this as a component of quantum. I > > believe HAProxy is one of the first supported services. It's likely > > not acting as a proxy, but we can probably write a plugin to make this > > work. > > > > - Ryan > > Publish a different DNS to the outside (balancer IP address) than from > inside wmflabs (including the balancer) ? > > _______________________________________________ > Labs-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/labs-l >
_______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
