I have a requirement where I want different subfolders on a domain to, potentially, hit different HTTP daemons. So http://test.com/somedir/ might hit Apache, but http://test.com/anotherdir/ might hit LigHTTPD. There may also be a 'default'. It has to be seamless, easily changeable, and "just work". Any suggestions?
Using Apache as the 'main' and then doing mod_proxy trickery just doesn't feel the fastest way to way, but I guess it's worth a try. There's also Perlbal, which is really for load balancing, but may be hackable to do what I want. Alternatively, I could write my own with Perl, some socket trickery, and just parse the HTTP requests before forwarding.
Squid, or similar, as a reverse proxy?
Posted by: Jamie Thingbox at January 31, 2006 04:34 PMyour design is broken. think of a sane way to do it.
Posted by: erwerrewrr at February 1, 2006 01:47 AMAnon: It's useful for situations where you've already committed to having certain URLs work, but need other URLs to work in a different way.
Am now thinking ProxyPass through Apache may be the most stable solution, though not the fastest.
Jamie: Perlbal is a reverse proxy, but yeah, I think this might be the route, but using the reverse proxy stuff in Apache.
Posted by: Peter Cooper at February 1, 2006 01:58 AMYou might be able to set a ScriptAlias in your Apache config to call the Lighttpd fastcgi for specific directories.
Posted by: damonp at February 1, 2006 02:43 AMWould it be possible to write your own reverse proxy in C/C++ instead of Perl, and thus in theory be more efficient?
Posted by: Ed at February 1, 2006 10:43 AMReturn to the homepage.
Privacy Policy