I'd like to redirect requests to other internal vservers so that I can
avoid the use of a reverse http proxy (since everything would be done
on the same Cherokee instance). However, it doesn't seem like it's
possible, according to Cherokee's documentation.

I believe this would be useful, so here's a use-case for it:


Imagine the following scenario, where there are two domain names:

http://internal.org
http://public.net

The first would only be used internally in a LAN, and the second would
be a global domain name.

The internal domain would already be setup to have a variety of
subdomains/sites (eg, "somesite.internal.org", "git.internal.org",
etc). But since "internal.org" is only available in the LAN, it can't
be accessed by the outside world.

That's where "public.net" comes in.

However, public.net doesn't support subdomain wildcards (if it did,
then listening as both "*.internal.org" and "*.public.net" would solve
this problem). So instead, this could be worked-around by setting
Cherokee to redirect to other internal vservers, using a (rough)
ruleset such as:

http://public.net/$1/$2  ->  http://$1.internal.org/$2

Which would result in requests being handled like this:

http://public.net/somesite  ->  http://somesite.internal.org
http://public.net/git  ->  http://git.internal.org
http://public.net/git/someproject  ->  http://git.internal.org/someproject



Thanks, and let me know what you think.
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to