Hi,
I want to use mod_proxy_http(reverse proxy) to forward the permissive
requests.
can i use mod_perl to check the requests before forward them by
mod_proxy_http?
Here below are my work environment.
Apache 2.2 + Mod_perl2 + mod_proxy + mod_proxy_http
Any advice will be appreciated.
Thanks.
André Warnier wrote:
Pavel Georgiev wrote:
Andre,
That is what I'm currently doing:
$request->content_type("multipart/x-mixed-replace;boundary=\"$this->{boundary}\";");
I don't think so. What you show above is a multipart message body,
which is not the same (and not the same level).
What
Pavel Georgiev wrote:
Andre,
That is what I'm currently doing:
$request->content_type("multipart/x-mixed-replace;boundary=\"$this->{boundary}\";");
I don't think so. What you show above is a multipart message body,
which is not the same (and not the same level).
What you are looking for is a
Andre,
That is what I'm currently doing:
$request->content_type("multipart/x-mixed-replace;boundary=\"$this->{boundary}\";");
and then each chuck of prints looks like this (no length specified):
for () {
$request->print("--$this->{boundary}\n");
$request->print("Content-type: text/html;
Pavel Georgiev wrote:
...
Let me make I'm understanding this right - I'm not using any buffers myself,
all I do is sysread() from a unix socked and print(),
its just that I need to print a large amount of data for each request.
...
Taking the issue at the source : can you not arrange to sys
Pavel
You're welcome. You are correct about the limitations of
Apache2::SizeLimit. Processes cannot be 'scrubbed'; rather they should
be killed and restarted.
Rapid memory growth should be prevented by prohibiting processes from
ever growing large than a preset limit. On Unix systems, the
Thank you both for the quick replies!
Arthur,
Apache2::SizeLimit is no solution for my problem as I'm looking for a way to
limit the size each requests take, the fact that I can scrub the process after
the request is done (or drop the requests if the process reaches some limit,
although my und
You could use Apache2::SizeLimit ("because size does matter") which
evaluates the size of Apache httpd processes when they complete HTTP
Requests, and kills those that grow too large. (Note that
Apache2::SizeLimit can only be used for non-threaded MPMs, such as
prefork.) Since it operates a
On Tue, Mar 16, 2010 at 3:33 AM, Matty Ronald wrote:
> Can any one please tell me how to disable perl's malloc in mod_perl?
>
> I donot want to recompile perl.
>
> Is there any way that i can disable perl's malloc in mod_perl only?
No, sorry. Since mod_perl is just embedding your perl in apache,
On Mon, Mar 15, 2010 at 11:26 PM, Pavel Georgiev wrote:
> I have a perl script running in mod_perl that needs to write a large amount
> of data to the client, possibly over a long period. The behavior that I
> observe is that once I print and flush something, the buffer memory is not
> reclaime
Hi,
Can any one please tell me how to disable perl's malloc in mod_perl?
I donot want to recompile perl.
Is there any way that i can disable perl's malloc in mod_perl only?
Regards,
Matty
Please add me to the mailing list
On Tue, Mar 16, 2010 at 12:58 PM, wrote:
> Hi! This is the ezmlm program. I'm managing the
> modperl@perl.apache.org mailing list.
>
> To confirm that you would like
>
> matty.r...@gmail.com
>
> added to the modperl mailing list, please send
> a short reply to
12 matches
Mail list logo