combination with SSL:
> https://stackoverflow.com/questions/9400068/make-timeout-work-for-lwpuseragent-https
>
> Best regards
> Andreas
>
>
> Am 13.05.2025 um 17:22 schrieb Joseph He:
>
> Andreas, thank you.
>
> On the client side, I set the timeout at LWP::UserAgent request t
have to be sure that the very first
> client which sent the very first request also waits long enough to let the
> application server make severals tries, therefore n * timeout.
>
> Best wishes
> Andreas
>
>
> Am 13.05.2025 um 16:46 schrieb Joseph He:
>
> Many thanks t
Apr 23, 2025, 3:38 PM Joseph He wrote:
>
>> On Apache2 doc, I found this. How does this timeout work? It looks like
>> it can only wait for 300 seconds before failing a request.
>>
>> https://httpd.apache.org/docs/2.0/mod/core.html#timeout
>> Description:
>
the http return status to make sure
> the client doesn't timeout waiting for the server to respond.
>
> On Wed, Apr 23, 2025, 2:19 PM Joseph He wrote:
>
>> Thanks, all.
>> Is that Apache timeout controlled by its configuration "Timeout"?
>> I don't
el timeouts.
>>
>> Declare only ONE instance responsible for a retry: Either the app server
>> calling the dispatcher with several tries or the dispatcher trying for
>> himself. Not both.
>>
>> Best regards
>> Andreas
>>
>>
>> Am 23.04.2025 um
All, good day.
Here is the issue I have.
My entire application is running on ModPerl/Apache environment.
I send Http::Request with data load from my App server to a dispatch server
thru LWP::UserAgent, I set the timeout 600 seconds.
The dispatch server is supposed to manipulate the data and send
g stdbuf with these options are to stream the ouput
> line after line, and not whatever terminal buffer is in place that will
> return the output in a chunk.
>
> However, all output from running the command ends up in the apache logs.
>
> That means that never gets anything, and t
via modperl <
modperl@perl.apache.org> wrote:
> That being said, is there a way to output to the web page in this scenario?
>
> On 14/5/24 12:15, Joseph He wrote:
> > CGI script runs on its own process. mod-perl basically wraps CGI script
> > into apache process
CGI script runs on its own process. mod-perl basically wraps CGI script
into apache process, that is why its output is automatically going to
Apache log.
On Mon, May 13, 2024 at 1:53 AM Steven Haigh via modperl <
modperl@perl.apache.org> wrote:
> Hi all,
>
> I'm playing around with mod_perl on ap
All, good day.
Our company wants to use some tool to do a static analysis on our Perl5
code like what they can do for Java, etc.
I know Perl::Critic can scan the code for the 'best practice'. Other than
this, anybody knows that there is another tool supposedly to help find the
security loopholes,
My company uses Perl for web development. It handles real time payment
transactions without any problem. Good software is made by the people not
by the language.
Joseph
On Tue, Aug 4, 2020 at 10:28 AM James Smith wrote:
>
>
>
>
> *From:* John Dunlap
> *Sent:* 04 August 2020 15:30
> *To:* Wesle
I think $str =~ /(\d+)\s(\d+)\s(??{$1*$2})/ should do it
My Perl version is v5.26.1
Joseph
On Wed, Jan 8, 2020 at 8:36 PM Wesley Peng wrote:
> Hello
>
> Give the case I have a string,
>
> $str = "2 3 6";
>
> I want to match with:
>
> true if $str =~ /(\d+)\s(\d+)\s($1*$2)/;
>
> that's to say
12 matches
Mail list logo