This may not be apache-dev related, but I do not know where else to ask it.
Is it possible to save an entire bucket bridade (including it's buckets)
across requests. I looked at ap_save_brigade, but I'm sure that will
work. It seems that the brigades are always tied to a connection.
Thanks.
Hello All,
I already read some emails about similar
problem
but i still get it even that i follow some
recomendations.
so i have curl library compiled with ssl support (
curl 7.10.8 , open ssl 0.9.7b )
on Interix SFU ( 3.5 ) and i have sendmail (
8.12.10 )
finaly i have plug-in for sendmai
On Wed, 7 Jan 2004, Brian Akins wrote:
> This may not be apache-dev related, but I do not know where else to ask it.
apache-modules maybe?
> Is it possible to save an entire bucket bridade (including it's buckets)
> across requests. I looked at ap_save_brigade, but I'm sure that will
> work.
Jeff Trawick wrote:
We use hsregex on older Solaris (2.0-2.5 or something like that).
Theoretically maybe something stops working or starts working when the
switch is made, but beyond that theoretical possibility does anyone have
real knowledge that there is a non-trivial likelihood of that occu
Nick Kew wrote:
ICBW here, but ...
Brigades are created on a pool. When the pool dies, so does the
brigade. Most brigades are created on the Request or Connection
pool, so die with the request or connection.
So, if I created a bridage like so:
bb =apr_brigade_create(r->server->pool, r->connec
On Wed, 7 Jan 2004, Brian Akins wrote:
> This may not be apache-dev related, but I do not know where else to ask it.
> Is it possible to save an entire bucket bridade (including it's buckets)
> across requests. I looked at ap_save_brigade, but I'm sure that will
> work. It seems that the brigad
On Wed, 7 Jan 2004, Brian Akins wrote:
> So, if I created a bridage like so:
>
> bb =apr_brigade_create(r->server->pool, r->connection->bucket_alloc);
>
> The brigade would stiil be "functional" after the connection went away?
> IOW, is a brigade dependent upon the buckuet_alloc after the brig
> Stas, we have closed a well known and remotely exploitable security leak. This
> goes straight over comfort. If you don't like it, provide an alternative
> solution. Just nagging or trying to talk the problem away doesn't help.
is creating a compile-time flag to disable the new-default behavior
Brian Akins wrote:
This may not be apache-dev related, but I do not know where else to ask it.
Is it possible to save an entire bucket bridade (including it's buckets)
across requests. I looked at ap_save_brigade, but I'm sure that will
work. It seems that the brigades are always tied to a co
Not entirely serious, but today, we actually hit this, in production :)
The hardware, a dual 2Ghz Xeon with 12Gb RAM with Linux 2.6.1-rc2 coped,
and remained responsive. So 20,000 may no longer be outside the realms
of what administrators reasonably desire to have.
Index: server/mpm/prefork/prefo
Attached are 2.0.48 numbers on RH AS 2.1 and 3.0.
Apache is build with worker MPM and default options on both versions.
C:
Apache is servicing more requests per sec on 2.1 on 1 and 2 CPUs, 3.0 is picking up the slack between 2 and 4 CPUs.
Prefork still serving static requests faster than worker
Hi, all
Our campany has an application server. We write an apache
module to direct certain extension file requests to our application server.
The module works fine funtionally. But recently we got some performance
problem. The module works fine by itself but it causes other cgi stuff -
per
On Thu, 8 Jan 2004, Jessica Wei wrote:
> Our campany has an application server. We write an apache module to
> direct certain extension file requests to our application server. The
> module works fine funtionally. But recently we got some performance
> problem. The module works fine by itself but
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2003/11/27 17:03:36 $]
Release:
1.3.30-dev: In development
1.3.29: Tagged October 24, 2003. Announced Oct 29, 2003.
1.3.28: Tagged July 16, 2003. Announced ??
1.3.27: Tagged September
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2004/01/07 02:49:45 $]
Release:
2.0.49 : in development
2.0.48 : released October 29, 2003 as GA.
2.0.47 : released July 09, 2003 as GA.
2.0.46 : released May 28, 2003 as GA.
APACHE 2.1 STATUS: -*-text-*-
Last modified at [$Date: 2004/01/04 15:08:00 $]
Release [NOTE that only Alpha/Beta releases occur in 2.1 development]:
2.1.0 : in development
Please consult the following STATUS files for information
on related proj
16 matches
Mail list logo
