Hello all, I hope this email finds you well.
I have recently opened a PR on apache httpd project (
https://github.com/apache/httpd/pull/385) . After upgrading to httpd
version 55, we have lost the capability to define a timeout for the health
check that is different from that of the request.
As
timeout value
To:
Hello,
Perhaps the dev list is a more appropriate place to bring this up. Cheers
El mar, 22 nov 2022 a las 9:39, Codeweavers ()
escribió:
> Hey Daniel,
>
> Would you be able to advise how I might push to get this change into
> 2.4.55? Or if there is someone I shou
> Am 24.09.2021 um 12:05 schrieb Ruediger Pluem :
>
>
>
> On 9/22/21 6:14 PM, Ruediger Pluem wrote:
>>
>>
>> On 9/22/21 5:41 PM, ste...@eissing.org wrote:
>>>
>>>> Am 22.09.2021 um 17:30 schrieb Ruediger Pluem :
>>>>
>&
On 9/22/21 6:14 PM, Ruediger Pluem wrote:
>
>
> On 9/22/21 5:41 PM, ste...@eissing.org wrote:
>>
>>> Am 22.09.2021 um 17:30 schrieb Ruediger Pluem :
>>>
>>> Currently we use the timeout setting of a virtual server hardcoded as the
>>>
On 9/22/21 5:41 PM, ste...@eissing.org wrote:
>
>> Am 22.09.2021 um 17:30 schrieb Ruediger Pluem :
>>
>> Currently we use the timeout setting of a virtual server hardcoded as the
>> beam timeout.
>> While I think that this is a good default I have situati
> Am 22.09.2021 um 17:30 schrieb Ruediger Pluem :
>
> Currently we use the timeout setting of a virtual server hardcoded as the
> beam timeout.
> While I think that this is a good default I have situations where I think it
> would be beneficial to set this timeout separatel
Currently we use the timeout setting of a virtual server hardcoded as the beam
timeout.
While I think that this is a good default I have situations where I think it
would be beneficial to set this timeout separately.
Opinions on a directive that allows to set this explicitly with a default of
Hi,
are there any plans to support openssl’s BIO_set_ssl_renegotiate_timeout and
BIO_set_ssl_renegotiate_bytes in mod_ssl’s config?
Please CC me on reply as I’m not subscribed to this list.
Thank you.
--
Pavel Janík
imeouts
* during pre_read_request(). If they appear elsewhere, just don't
* check or extend the time since they won't block and we'll see the
* bytes again later
*/
return ap_get_brigade(f->next, bb, mode, block, readbytes);
}
in req
) OpenSSL/1.0.2d
Content-Length: 0
Connection: close
Content-Type: text/html
From a short run with GDB, it looks like the "standard" output filter
chain is not being disabled in this timeout case.
(Now that mod_http2 is (almost) released, if you'd prefer I move this to
the bug tracke
mod_proxy when
ProxyTimeout isn't configured?
Anyway, +1 for syncing the default config for Timeout with the internal
default.
--
Born in Roswell... married an alien...
http://emptyhammock.com/
Is 300 good for anyone? The hard-coded default is 60 which seems awfully
high to me already.
--
Eric Covener
cove...@gmail.com
meout == UNSET ?
SSL_SESSION_CACHE_TIMEOUT : sc->session_cache_timeout);
(As a side effect, this would also make sure that the timeout for
TLS session tickets is 300 seconds for all SSLProtocol settings,
if SSLSessionCacheTimeout is not explicitly configured.)
Applied to trunk together with a small docs exte
On 14.06.2014 12:53, Rainer Jung wrote:
> SSL_CTX_set_timeout() seems to work pretty well.
Indeed. I missed the fact that after the ticket has been decrypted/processed,
there's a timeout check in ssl_sess.c:ssl_get_prev_session(), based on the
SSL_SESSION's "time" value, wh
gt;> such a ticket may be used by the client. As far as I can see, there is
>>> no specific API in OpenSSL for that, but there is a general API allowing
>>> to set a session timeout that is checked whenever a session is
>>> reconstructed.
>>
>> Wha
gt;> no specific API in OpenSSL for that, but there is a general API allowing
>> to set a session timeout that is checked whenever a session is
>> reconstructed.
>
> What OpenSSL function do you have in mind? SSL_SESSION_set_timeout?
I was hoping SSL_CTX_set_timeout() would do t
RFC (session resumption is a standard protocol feature).
> Currently mod_ssl does not provide a way to control the time how long
> such a ticket may be used by the client. As far as I can see, there is
> no specific API in OpenSSL for that, but there is a general API allowing
> to set a
On Fri, Jun 13, 2014 at 5:19 PM, Eric Covener wrote:
> On Fri, Jun 13, 2014 at 11:03 AM, Plüm, Rüdiger, Vodafone Group
> wrote:
>>> I would prefer to keep SSLSessionCacheTimeout the only directive and use
>>> that also for the default timeout of any created session even
On Fri, Jun 13, 2014 at 11:03 AM, Plüm, Rüdiger, Vodafone Group
wrote:
>> I would prefer to keep SSLSessionCacheTimeout the only directive and use
>> that also for the default timeout of any created session even if not
>> cached server side. Second best IMHO would be a separ
> -Ursprüngliche Nachricht-
> Von: Rainer Jung > Gesendet: Freitag, 13. Juni 2014 16:55
> An: dev@httpd.apache.org
> Betreff: mod_ssl SSL session timeout
>
> I would prefer to keep SSLSessionCacheTimeout the only directive and use
> that also for the defaul
control the time how long
such a ticket may be used by the client. As far as I can see, there is
no specific API in OpenSSL for that, but there is a general API allowing
to set a session timeout that is checked whenever a session is
reconstructed. The timeout can be inherited from the SSL_CTX so it
On Thu, Mar 6, 2014 at 2:17 AM, InuSasha wrote:
> i have actual an problem with my proxy-timeout configuration.
> (Apache 2.2.26, but 2.4 seems to have the same problem).
Try us...@httpd.apache.org
Hi,
i have actual an problem with my proxy-timeout configuration.
(Apache 2.2.26, but 2.4 seems to have the same problem).
In my apache configuration we have defined a global ProxyTimeout to 30
seconds.
But one of our JBoss-backends have some slow pages, and we want to raise
the timeout to 2
+1...
On Feb 18, 2014, at 9:29 AM, Eric Covener wrote:
> I think this needs to be handled as 1 API within event, taking the
> existing API and adding a timeout, rather than having the caller
> register separate timed callbacks.
>
> This way, event can mark the timeout as n
I think this needs to be handled as 1 API within event, taking the
existing API and adding a timeout, rather than having the caller
register separate timed callbacks.
This way, event can mark the timeout as no longer needed before
pushing the first event to the worker. This way there'
There is a deficiency in the asynch websocket stuff in trunk.
For background, the websockets proxy acts like mod_proxy_connect after
the initial setup. It can ask event to watch both sockets for it and
return SUSPENDED.
But there is no separate timeout if neither end sees activity, so the
Hi,
that's connected to PR 54973. apr_poll in mod_proxy_fcgi dispatch method
uses hard-coded 30s timeout if "timeout=XX" is not set in ProxyPass
directive.
Attached patch uses apr_socket_timeout_get(conn->sock) as default
timeout, so it's possible to set this part
On Mon, Aug 5, 2013 at 7:19 AM, Faidon Liambotis wrote:
> "timeout" is nowadays a duration, not an absolute value. Fix the trace2
> output to print it as such, instead of subtracting time(NULL) and
> resulting in lines such as:
>
> [Mon Aug 05 03:51:07.369625 2013] [
"timeout" is nowadays a duration, not an absolute value. Fix the trace2
output to print it as such, instead of subtracting time(NULL) and
resulting in lines such as:
[Mon Aug 05 03:51:07.369625 2013] [ssl:trace2] [pid 7916:tid 140003006699264]
ssl_engine_kernel.c(1698): Inter-Proce
Quick use case solved by adding a simple note in the request and
checking for it later: Take a backend BalancerMember out of service if a
read timeout occurs.
This is nearly identical to the failonstatus parameter. I'm thinking
"failontimeout" would be the most consistent. Any opp
, dbuf, sbuf, bb, script_err);
Now, if the script does not generate any output not even headers
ap_scan_script_header_err_brigade() polls the script's stdout and stderr
until the timeout is reached. Then log_script() is called which calls
discard_script_output() and, thus, again ends
Hi,
When some vhost's scripts exhaust all process slots available to it
(FcgidMaxProcessesPerClass),
next requests are waiting for over 60 seconds before issuing 503 error.
I came across this while modifying suexec to use cgroups to provide
better resource separation for use in our shared hosting
On 21.11.2011 11:59, "Plüm, Rüdiger, VF-Group" wrote:
-Original Message-
From: Steffen [mailto:i...@apachelounge.com]
Sent: Montag, 21. November 2011 11:50
To: dev@httpd.apache.org
Subject: Win 2.3.15 :: The timeout specified has expired
Observing that the error.log is fi
On Monday 21 November 2011, Reindl Harald wrote:
> > Steffen, the default for Timeout has been reduced from 300 to 60.
> > If you get complaints from users, the new value may be too low
> > and we should maybe reconsider the new value.
>
> hi
>
> we are using &quo
Am 21.11.2011 19:17, schrieb Stefan Fritsch:
> On Monday 21 November 2011, William A. Rowe Jr. wrote:
>> On 11/21/2011 4:49 AM, Steffen wrote:
>>> Observing that the error.log is filling with [http:error] lines,
>>> never seen with 2.2:
>>>
>>> [http:
On Monday 21 November 2011, William A. Rowe Jr. wrote:
> On 11/21/2011 4:49 AM, Steffen wrote:
> > Observing that the error.log is filling with [http:error] lines,
> > never seen with 2.2:
> >
> > [http:error] [pid 3244:tid 2656] (70007)The timeout specified has
> &
On 11/21/2011 4:49 AM, Steffen wrote:
Observing that the error.log is filling with [http:error] lines, never seen
with 2.2:
[http:error] [pid 3244:tid 2656] (70007)The timeout specified has expired:
[client
114.79.60.32:11091] Timeout while writing data for URI
/download/binaries/httpd-2.2.21
Should be the normal "Timeout" parameter.
Ah was not aware of that one.
Is logging now, good.
-Original Message-
From: Steffen [mailto:i...@apachelounge.com]
Sent: Montag, 21. November 2011 11:50
To: dev@httpd.apache.org
Subject: Win 2.3.15 :: The timeout specified h
> -Original Message-
> From: Steffen [mailto:i...@apachelounge.com]
> Sent: Montag, 21. November 2011 11:50
> To: dev@httpd.apache.org
> Subject: Win 2.3.15 :: The timeout specified has expired
>
> Observing that the error.log is filling with [http:error]
> l
Observing that the error.log is filling with [http:error] lines, never seen
with 2.2:
[http:error] [pid 3244:tid 2656] (70007)The timeout specified has expired:
[client 114.79.60.32:11091] Timeout while writing data for URI
/download/binaries/httpd-2.2.21-win32-x86-ssl.zip to the client
On Mon, Nov 14, 2011 at 11:12 AM, Paul Querna wrote:
>
> The problem became that in trunk, we had to told the lock for the
> timeout queues while we were doing the pollset operation. The
> pollset already had its own internal mutex too, for its own rings. So
> we were double
ng latency to the Add
> operations? It probably doesn't matter so much for Remove because we are
> done with the connection.
The problem became that in trunk, we had to told the lock for the
timeout queues while we were doing the pollset operation. The
pollset already had its ow
are
done with the connection.
> This would remove the 4 or 5 separate timeout queues we have
> developed, and their associated mutex, and basically move all of the
> apr_pollset operations to the single main thread.
>
The 4 or 5 separate queues give us a simple and cheap way to know when the
x at all.
>>
>> My current 'best' idea I think:
>>
>> 1) Create a new struct, ap_pollset_operation_and_timeout_info_t, which
>> contains a what pollset operation to do (Add, Remove, Flags),
>> timeout_type, the timeout value, and a pointer to t
.
>
> My current 'best' idea I think:
>
> 1) Create a new struct, ap_pollset_operation_and_timeout_info_t, which
> contains a what pollset operation to do (Add, Remove, Flags),
> timeout_type, the timeout value, and a pointer to the conn_rec.
>
> 2) Implement a single-reader single writer circu
On Sat, 12 Nov 2011, Stefan Fritsch wrote:
locking for the timeout queues. But what we really should do in 2.4.0 is
remove all the MPM-implementation specific details from conn_state_t. The
only field that is actually used outside of the MPMs is 'state'. If we make
the rest non-
On Fri, 11 Nov 2011, Paul Querna wrote:
After r1201149, we now lock for lots of things, where in an ideal
case, we shouldn't need it.
I agree that that's not optimal, but it is no regression. Event always
used locking for the timeout queues. But what we really should do in 2.4.0
hich
contains a what pollset operation to do (Add, Remove, Flags),
timeout_type, the timeout value, and a pointer to the conn_rec.
2) Implement a single-reader single writer circular ring buffer of
these structures. (Using 2x uint16_t head/end offsets stuffed into a
single uint32_t so we can make i
On 6/11/2010 2:45 PM, William A. Rowe Jr. wrote:
>
> * Replace mod_proxy_http.so with a patched version, for source code
> see http://www.apache.org/dist/httpd/patches/apply_to_2.2.15/ or
> http://www.apache.org/dist/httpd/patches/apply_to_2.3.5/ and for
> binaries see the ht
Vulnerability; httpd Timeout detection flaw (mod_proxy_http) CVE-2010-2068
Classification; important
Description;
A timeout detection flaw in the httpd mod_proxy_http module causes
proxied response to be sent as the response to a different request,
and potentially served to a
William A. Rowe, Jr. wrote:
Mladen Turk wrote:
To clarify, it's no longer possible to pipe 'hugefile' through
rotatelogs with 1MB granularity. This should at least be noted
in the docs if the patch is accepted.
Jim is traveling, it would be good to get his feedback Monday
on your proposed patc
rrent file and timeout for that
period of time?
Might be a nice add-on.
However it would require reorganizing the rotate logic to calculate
early instead late. This would complicate the patch and it
would be hard to follow the difference.
I've choose a straight forward approach.
Regards
--
^(TM)
Mladen Turk wrote:
> Dan Poirier wrote:
>> Would wait_for_io_or_timeout() be a good candidate for apr?
>>
>
> There is apr_wait_for_io_or_timeout but it uses the
> apr_file_t->timeout which can be set only for pipes
> and sockets.
>
> Also the Win32 code w
Mladen Turk wrote:
>
> Code was testes both on windows and linux and it works like
> a charm (rotation is done at exact time regardless of log events).
Foolish question, but rather than waking up every second, isn't it more
rational to compute the expiry of the current file and ti
Plüm, Rüdiger, VF-Group wrote:
Any particular reason why not using apr_wait_for_io_or_timeout
at least on unix?
See the answer I gave to Dan.
It uses file internal timeout which we cannot set, so no
it cannot be used.
Regards
--
^(TM)
Dan Poirier wrote:
Would wait_for_io_or_timeout() be a good candidate for apr?
There is apr_wait_for_io_or_timeout but it uses the
apr_file_t->timeout which can be set only for pipes
and sockets.
Also the Win32 code will work only for stdhandles because
they are pipes.
In essence the ans
Any particular reason why not using apr_wait_for_io_or_timeout
at least on unix?
Regards
Rüdiger
> -Ursprüngliche Nachricht-
> Von: Mladen Turk
> Gesendet: Mittwoch, 10. Juni 2009 14:24
> An: dev@httpd.apache.org
> Betreff: Re: rotatelogs - Adding timeout for rea
Would wait_for_io_or_timeout() be a good candidate for apr?
--
Dan Poirier
cific.
Attached is the patch that uses 1 second timeout when reading
from stdin (hard-coded because we have 1 second rotation resolution).
Unfortunately I had to make WIN32 specific peace of code,
cause we don't have APR_FILES_AS_SOCKETS on that platform.
Code was testes both on windows and linux an
William A. Rowe, Jr. wrote:
Mladen Turk wrote:
Why? Timeout on reading from stdin is a nice and clean way for making the
rotation to happen even when there is no log entries fired that would
break the block on stdin. Rotation would always happen at midnight,
not at some random point of time in
On 09.06.2009 18:51, William A. Rowe, Jr. wrote:
> Mladen Turk wrote:
>> Why? Timeout on reading from stdin is a nice and clean way for making the
>> rotation to happen even when there is no log entries fired that would
>> break the block on stdin. Rotation would always happe
Mladen Turk wrote:
>
> Why? Timeout on reading from stdin is a nice and clean way for making the
> rotation to happen even when there is no log entries fired that would
> break the block on stdin. Rotation would always happen at midnight,
> not at some random point of time in
ear from Jim what he proposes
for rotatelogs solution for holding the file handles in parent.
There should be no parent vs child question here. The right fix is
one process, just as on unix. Windows bubblegum and bailing wire is
the wrong fix.
Why? Timeout on reading from stdin is a nice and
;) loop giving change to rotate
> logic to handle the files.
>
> For Windows we can use apr_file_pipe_timeout_set(f_stdin, ...
> Dunno if there's a bug in APR/win32, but you can actually always
> set a timeout on a apr_file_t unlike on unix where this
> is possible only if apr_fi
APR_TIMEUP it's
just a continue in the for (;;) loop giving change to rotate
logic to handle the files.
For Windows we can use apr_file_pipe_timeout_set(f_stdin, ...
Dunno if there's a bug in APR/win32, but you can actually always
set a timeout on a apr_file_t unlike on unix where this
Mladen Turk wrote:
> Hi,
>
> Currently rotatelogs (at least on windows) holds the initial
> log file by parent process (well it tries to rotate if something
> is written from parent which is impossible for access logs).
>
> I plan to use the apr_wait_for_io_or_timeout before calling
> the apr_fil
Hi,
Currently rotatelogs (at least on windows) holds the initial
log file by parent process (well it tries to rotate if something
is written from parent which is impossible for access logs).
I plan to use the apr_wait_for_io_or_timeout before calling
the apr_file_read(f_stdin, ...). This would g
his thread
[http://marc.info/?l=apache-httpd-dev&m=122358323701009&w=2] and the
connection timeout then worked on Windows as expected with 8 dead
ports being checked in between 1 and 2 seconds -- which is what I'd
expect given a connectiontimeout of 160ms.
It would seem proxy_util.
x27;s suggested fix from earlier in this
thread [http://marc.info/?l=apache-httpd-dev&m=122358323701009&w=2] and
the connection timeout then worked on Windows as expected with 8 dead
ports being checked in between 1 and 2 seconds -- which is what I'd
expect given a connectiontimeout of
x=40 ttl=900 keepalive=Off timeout=9 retry=30
>connectiontimeout=160ms flushpackets=on
>
>BalancerMember ajp://localhost:8011 route=tomcat2 min=16 max=80
> smax=40 ttl=900 keepalive=Off timeout=9 retry=30
>connectiontimeout=160ms flushpackets=on
>
The errno assignments you added did the trick.
Unfortunately, I'm still missing the overall goal. I have many proxy
balance members like:
BalancerMember ajp://localhost:8010 route=tomcat1 min=16 max=80
smax=40 ttl=900 keepalive=Off timeout=9 retry=30
connectiontimeout=
jp://localhost:8010 route=tomcat1 min=16 max=80
smax=40 ttl=900 keepalive=Off timeout=9 retry=30
connectiontimeout=160ms flushpackets=on
Regards
Rüdiger
er ajp://localhost:8010 route=tomcat1 min=16 max=80
> smax=40 ttl=900 keepalive=Off timeout=9 retry=30
> connectiontimeout=160ms flushpackets=on
Regards
Rüdiger
something like:
BalancerMember ajp://localhost:8010 route=tomcat1 min=16 max=80
smax=40 ttl=900 keepalive=Off timeout=9 retry=30
connectiontimeout=160ms flushpackets=on
--
Jess Holle
On 10/15/2008 05:57 PM, Mladen Turk wrote:
> Ruediger Pluem wrote:
>>
>>>
>>> This would be similar what we have for parsing some
>>> file sizes across the conf (1024, 1K, 1M, ...)
>>>
>>> I'm not aware of any standard defining that, but
>>> since we underneath use apr_time anything
>>> from 1us
Mladen Turk wrote:
Ruediger Pluem wrote:
This would be similar what we have for parsing some
file sizes across the conf (1024, 1K, 1M, ...)
I'm not aware of any standard defining that, but
since we underneath use apr_time anything
from 1us should be valid time (weather it makes
sense is a diffe
Ruediger Pluem wrote:
This would be similar what we have for parsing some
file sizes across the conf (1024, 1K, 1M, ...)
I'm not aware of any standard defining that, but
since we underneath use apr_time anything
from 1us should be valid time (weather it makes
sense is a different story).
Ho
ome more advanced function for parsing the
> time should be added thought.
> Eg.
> timeout=30 (defaults to seconds)
> timeout=30ms
> timeout=30us
> timeout=30s[ec]
> timeout=1min
> timeout=1h
>
> This would be similar what we have for parsing some
> file sizes across
Ruediger Pluem wrote:
I guess this leaves us to the question whether we need to be able to set
connectiontimeouts below one second.
Right now we are using a simple atoi for parsing those
config values. Some more advanced function for parsing the
time should be added thought.
Eg.
timeout=30
Ruediger Pluem wrote:
I checked 2.2.x and trunk in the meantime and they behaves as they should
*without* the patch.
If I try to connect to a non existing host the apr_socket_connect call returns
after the timeout set via connectiontimeout.
I guess this leaves us to the question whether we need
occurred, loop round and try again */
>> if (rv != APR_SUCCESS) {
>> apr_socket_close(newsock);
>>
>
> Have you really checked that this patch solves your problem and that the
> problem
> is not solved without?
> While rev
the problem
is not solved without?
While reviewing this patch for backport I noticed that it is wrong and that it
shouldn't
be needed. The call to apr_socket_timeout_set before apr_socket_connect already
sets the
socket to non-blocking mode because the timeout of the socket is -1 after
crea
On 10/09/2008 10:11 PM, Matt Stevenson wrote:
> Had a bit more time, here is a patch that should work for Unix which have
> "apr_wait_for_io_or_timeout" available. I can't test windows/others so that's
> the reason for the ifdef.
>
> ProxyPass / balance://hotcluster/
>
> # defaultish tomcat
On 10/09/2008 10:11 PM, Matt Stevenson wrote:
> Had a bit more time, here is a patch that should work for Unix which have
> "apr_wait_for_io_or_timeout" available. I can't test windows/others so that's
> the reason for the ifdef.
>
> ProxyPass / balance://hotcluster/
>
> # defaultish tomcat
gards
matt
- Original Message
From: Matt Stevenson <[EMAIL PROTECTED]>
To: dev@httpd.apache.org
Sent: Wednesday, October 8, 2008 9:55:43 PM
Subject: proxy_ajp connect timeout fix.
Hi,
I've used mod_jk (1/2) for years. I've always had an issue when a backend
server go
ooked deeper into the apr
libs
(sorry its not in diff format, and for the hard 2 sec timeout). The
code seems to work fine for linux (and probably other
unix). I've basically redone the apr code in
apr_wait_for_io_or_timeout (should have dug deeper first).
Anyway the current release code d
per into the apr libs
> (sorry its not in diff format, and for the hard 2 sec timeout). The code
> seems to work fine for linux (and probably other
> unix). I've basically redone the apr code in apr_wait_for_io_or_timeout
> (should have dug deeper first).
>
> Anyway the cur
sumes that apr_socket_timeout_set works for all
connects. I don't believe it does, not unless it is in non blocking mode. I
wrote the code below for"ap_proxy_connect_backend" before I looked deeper into
the apr libs (sorry its not in diff format, and for the hard 2 sec timeout).
The code see
Hi,
up to the release of apache 2.2.4 the 'timeout' parameter of the
BalancerMember directive would affect only the connection timout to the
backend servers. This allowed to set reasonably small timeout
values(let's say 1 or 2 seconds) in a scenario where the balancer and
the
Hi,
I have noted that ap_proxy_connect_backend() may behave "strange" when
using ping=val with AJP.
The timeout are used in the order worker->timeout, conf->timeout and
s->timeout.
The problem I have is that I want to do a AJP cping/cpong with the
ping=timeout... That
As a way to apologize for my 'spamming', I think I've
uncovered the issue. This is either a bug, a known
limitation or a misunderstanding on my part of the
purpose of ProxyTimeout.
Turns out that timeout is set on the socket in two places:
first when it's attempting to get t
uot;Hello"
echo ""
echo "Hello"
echo ""
Why doesn't this timeout?
For 'fun', I' fiddled with the code, namely proxy_http.c,
right before the call to ap_proxy_connect_to_backend, I
reduce the value of 'timeout' in the conf struct
Hmmm, sorted out why timeout was showing as 0. Should have just used
APR_TIME_T_FMT in the first place instead of guessing what format was
supposed to be.
Anyway, issue still stands as detailed at end of mail that mod_cgid
seems to lack setting of timeout on socket, plus the issue of deadlock
The function in server/core.c called for the Timeout directive is:
static const char *set_timeout(cmd_parms *cmd, void *dummy, const char *arg)
{
const char *err = ap_check_cmd_context(cmd,
NOT_IN_DIR_LOC_FILE|NOT_IN_LIMIT);
if (err != NULL) {
return err;
}
cmd->ser
When I run some Flood tests I am getting timeout errors. It appears
as if Flood kills threads if they encounter a timeout on a given url
in a urllist, even if it hasn't reached the end of the list. Where is
this timeout value set, and is it possible for me to change this
value so t
On 05/29/2007 08:42 PM, Andy Wang wrote:
> We noticed that with mod_proxy_ajp, it's not possible to set an
> indefinite timeout like was possible with mod_jk. So a long running JSP
> page, for example:
> <% Thread.sleep(96); %>
>
> With mod_proxy_ajp timeout s
We noticed that with mod_proxy_ajp, it's not possible to set an
indefinite timeout like was possible with mod_jk. So a long running JSP
page, for example:
<% Thread.sleep(96); %>
With mod_proxy_ajp timeout set to 300 will cause a 503 to be thrown back
to the client since mod_
script stopped reading, soak up remaining message */
child_stopped_reading = 1;
}
In the comment it says 'until done or too much time elapses with no
progress'. That it mentions time suggests it perhaps uses some timeout
mechanism, but I can't find any e
> -Ursprüngliche Nachricht-
> Von: Lucas Brasilino
> Gesendet: Dienstag, 23. Januar 2007 14:43
> An: dev@httpd.apache.org
> Betreff: Re: setting request timeout in mod_proxy/mod_proxy_balancer
>
> > Based on your configuration from above, the following should w
Hi
> Based on your configuration from above, the following should work:
No, it doesn't. I've tried yet.
>From docs:
'Connection timeout in seconds. If not set the Apache
will wait until the free connection is available. This
directive is used for limiting the number of conne
1 - 100 of 165 matches
Mail list logo
