>Bob Foster wrote:
>> It's a application which has grown awkward
>> with age. The way the url is stored in the database and then handled by
>> our perl scripts doesn't like the url getting passed to port 8080.
>We're
>> in the process of figuring out what to do to make everything work with
>> mod_perl being the backend.
>
>theo@omniti.com wrote:
>BTW, I would wager money that backhand can make that problem disappear.
>It
>doesn't do any URL modification ala mod_proxy/mod_rewrite.
>
>Though mod_backhand doesn't amke it trivial to set it up as a proxy only
>(frontend->backend) on the same machine, it is _much_ more efficient than
>mod_proxy (due to the restrictions placed on you -- that frakly should
>inhibit
>you in any way).
>
>If you have only one machine, and you ran Apache/mod_backhand on the front
>interface and Apache/mod_perl on the 127.0.0.1 or backend interface, you
>can
>serve GIF's and static content of the mod_backhand and have it proxy
>mod_perl
>content to the backend instance transparently.
This is what I'd like to try first! However, after spending several hours
reading the FAQ and other documentation, and trying a bunch of things, I
realize that I'm going to need more help.
I established the mod_perl backend with the command:
Listen 127.0.0.1:8080 Is this the correct way to do that? I can
run perl-status from a browser on this same box and see it fine.
I added the following on the mod_backhand frontend:
<Directory /cgi-bin/>
Backhand HTTPRedirectToIP 127.0.0.1:8080
</Directory>
This MUST be wrong but it was my best guess. NOTHING ever gets redirected
to the backend.
>
>The advantage of this over mod_proxy is that even if you have Keep Alives
>disabled on the front end (as most high traffic Apache installations are
>forced to), mod_backhand will "upgrde" the HTTP session to use Keep
>Alives and
>keep a connection pool to the backend instances. Much.. much.. much..
>faster.
>
>Becuase mod_backhand does no URL rewriting (not even port info), the
>mod_perl
>instance can actually serve content as if it is listening on the external
>interface; the remote IP and URL will be preserved transparently :-)
>
This sounds great if I can get it to work. Your help is greatly
appreciated!
Bob Foster
System Administrator
Dissemination, Inc.
Hotresponse.com
(541) 617-5021
bob@hotresponse.com
>> It's a application which has grown awkward
>> with age. The way the url is stored in the database and then handled by
>> our perl scripts doesn't like the url getting passed to port 8080.
>We're
>> in the process of figuring out what to do to make everything work with
>> mod_perl being the backend.
>
>theo@omniti.com wrote:
>BTW, I would wager money that backhand can make that problem disappear.
>It
>doesn't do any URL modification ala mod_proxy/mod_rewrite.
>
>Though mod_backhand doesn't amke it trivial to set it up as a proxy only
>(frontend->backend) on the same machine, it is _much_ more efficient than
>mod_proxy (due to the restrictions placed on you -- that frakly should
>inhibit
>you in any way).
>
>If you have only one machine, and you ran Apache/mod_backhand on the front
>interface and Apache/mod_perl on the 127.0.0.1 or backend interface, you
>can
>serve GIF's and static content of the mod_backhand and have it proxy
>mod_perl
>content to the backend instance transparently.
This is what I'd like to try first! However, after spending several hours
reading the FAQ and other documentation, and trying a bunch of things, I
realize that I'm going to need more help.
I established the mod_perl backend with the command:
Listen 127.0.0.1:8080 Is this the correct way to do that? I can
run perl-status from a browser on this same box and see it fine.
I added the following on the mod_backhand frontend:
<Directory /cgi-bin/>
Backhand HTTPRedirectToIP 127.0.0.1:8080
</Directory>
This MUST be wrong but it was my best guess. NOTHING ever gets redirected
to the backend.
>
>The advantage of this over mod_proxy is that even if you have Keep Alives
>disabled on the front end (as most high traffic Apache installations are
>forced to), mod_backhand will "upgrde" the HTTP session to use Keep
>Alives and
>keep a connection pool to the backend instances. Much.. much.. much..
>faster.
>
>Becuase mod_backhand does no URL rewriting (not even port info), the
>mod_perl
>instance can actually serve content as if it is listening on the external
>interface; the remote IP and URL will be preserved transparently :-)
>
This sounds great if I can get it to work. Your help is greatly
appreciated!
Bob Foster
System Administrator
Dissemination, Inc.
Hotresponse.com
(541) 617-5021
bob@hotresponse.com