You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by wi <ic...@gmail.com> on 2009/03/11 21:34:35 UTC
[users@httpd] Dynamically Updating Rewrite rules etc.
Hi all
Our architecture has a cluster of Apache servers behind an industrial
strength load balancer. The Apache servers basically examine each
request (REST requests, actually) and dispatch to back end
applications depending on this parsing.
At this stage, each back-end application has to be set up in the
Apache configuration manually. In other words, we add rewrite rules
and proxy accordingly. Although the server configuration is propagated
out easily enough, it still requires a restart of each Apache server.
It would be nice if there was a way to dynamically update this routing
information without having to resort to updating configuration for
each server (even though they're all the same). What would be even
nicer is if each back-end application could publish/broadcast it's
existence and for the Apache servers to pick this up. Without getting
into complicated LDAP stuff, has anyone seen this type of setup and
solution before?
--
Cheers
Wayne
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Dynamically Updating Rewrite rules etc.
Posted by wi <ic...@gmail.com>.
Thanks for the suggestion - this looks promising.
cheers
Wayne
On Thu, Mar 12, 2009 at 3:37 AM, Krist van Besien
<kr...@gmail.com> wrote:
> On Wed, Mar 11, 2009 at 9:34 PM, wi <ic...@gmail.com> wrote:
>>
>> It would be nice if there was a way to dynamically update this routing
>> information without having to resort to updating configuration for
>> each server (even though they're all the same). What would be even
>> nicer is if each back-end application could publish/broadcast it's
>> existence and for the Apache servers to pick this up. Without getting
>> into complicated LDAP stuff, has anyone seen this type of setup and
>> solution before?
>
> One solution would be to use rewrite maps. Apache keeps these maps in
> memory, but reloads them whenever they change on disk. You could make
> the backend produce this rewrite map and push a new one on your apache
> server whenever this changes.
>
> Krist
>
> --
> krist.vanbesien@gmail.com
> krist@vanbesien.org
> Bremgarten b. Bern, Switzerland
> --
> A: It reverses the normal flow of conversation.
> Q: What's wrong with top-posting?
> A: Top-posting.
> Q: What's the biggest scourge on plain text email discussions?
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
--
Cheers
Wayne
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Dynamically Updating Rewrite rules etc.
Posted by Krist van Besien <kr...@gmail.com>.
On Wed, Mar 11, 2009 at 9:34 PM, wi <ic...@gmail.com> wrote:
>
> It would be nice if there was a way to dynamically update this routing
> information without having to resort to updating configuration for
> each server (even though they're all the same). What would be even
> nicer is if each back-end application could publish/broadcast it's
> existence and for the Apache servers to pick this up. Without getting
> into complicated LDAP stuff, has anyone seen this type of setup and
> solution before?
One solution would be to use rewrite maps. Apache keeps these maps in
memory, but reloads them whenever they change on disk. You could make
the backend produce this rewrite map and push a new one on your apache
server whenever this changes.
Krist
--
krist.vanbesien@gmail.com
krist@vanbesien.org
Bremgarten b. Bern, Switzerland
--
A: It reverses the normal flow of conversation.
Q: What's wrong with top-posting?
A: Top-posting.
Q: What's the biggest scourge on plain text email discussions?
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org