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
> >>
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 wit
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 /proxy_url=htt
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
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 sam
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 -
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
I have a site that does secure credit card transactions on behalf of
merchants. As soon as a cardholder on the merchant site is ready to pay,
the merchant redirects the cardholder to my site, and I pick up payment
details from the cardholder directly over SSL.
When the cardholder is accessing
