Marius Kjeldahl wrote:
Any other ways of accomplishing the same without the added overhead of
my perl module?
There was an example in the eagle-book, AFAIR, you need to build a
custom PerlTranslateHandler and rewrite the filename to the url of your
customer and use $r-handler(mod-proxy),
On Fri, 15 Mar 2002, Marius Kjeldahl wrote:
Any other ways of accomplishing the same without the added overhead of
my perl module?
You can use
1. mod_proxy:
ProxyPass /images/http://image.site/image/
2. mod_accel:
AccelPass /images/http://image.site/image/
3. default-handler -
I guess these all suffer from the fact that the parameters have to be
specified in httpd.conf, which makes it impossible to pass a url to
fetch from in a parameter, right?
Marius K.
Igor Sysoev wrote:
On Fri, 15 Mar 2002, Marius Kjeldahl wrote:
Any other ways of accomplishing the same
On Fri, 15 Mar 2002, Igor Sysoev wrote:
On Fri, 15 Mar 2002, Marius Kjeldahl wrote:
Any other ways of accomplishing the same without the added overhead of
my perl module?
You can use
1. mod_proxy:
ProxyPass /images/http://image.site/image/
I'd go for this, perhaps with
On Fri, 15 Mar 2002, Marius Kjeldahl wrote:
I guess these all suffer from the fact that the parameters have to be
specified in httpd.conf, which makes it impossible to pass a url to
fetch from in a parameter, right?
So mod_rewite with mod_proxy or mod_accel:
RewriteRule
At 05:11 PM 3/15/2002 +0300, Igor Sysoev wrote:
On Fri, 15 Mar 2002, Marius Kjeldahl wrote:
I guess these all suffer from the fact that the parameters have to be
specified in httpd.conf, which makes it impossible to pass a url to
fetch from in a parameter, right?
So mod_rewite with
On Fri, 15 Mar 2002, Bill Moseley wrote:
At 05:11 PM 3/15/2002 +0300, Igor Sysoev wrote:
On Fri, 15 Mar 2002, Marius Kjeldahl wrote:
I guess these all suffer from the fact that the parameters have to be
specified in httpd.conf, which makes it impossible to pass a url to
fetch from in
