Okay good, thanks for your feedback.
A.T.
2016-02-22 11:57 GMT+01:00 Oliver Graute :
> On 19/02/16, Oliver Graute wrote:
> > On 19/02/16, Aurélien Terrestris wrote:
> > > Hello,
> > >
> > > I'm not sure we can accept only one connection at a given time.
> > > I tested with the "prefork MPM", and
On 19/02/16, Oliver Graute wrote:
> On 19/02/16, Aurélien Terrestris wrote:
> > Hello,
> >
> > I'm not sure we can accept only one connection at a given time.
> > I tested with the "prefork MPM", and I only achieve 1 concurrent request
> > being processed at a given time and all others requests ar
In een bericht van 19-2-2016 8:50:
For testing, or for long-term behavior?
for long-term behavior, its a requirement by the costumer.
Just validate on ip number and block accordingly all other ports for
http(s) access
/Jos
--
On 19/02/16, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Oliver,
>
> On 2/19/16 10:11 AM, Oliver Graute wrote:
> > On 19/02/16, Aurélien Terrestris wrote:
> >> Hello,
> >>
> >> I'm not sure we can accept only one connection at a given time. I
> >> tested with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oliver,
On 2/19/16 10:11 AM, Oliver Graute wrote:
> On 19/02/16, Aurélien Terrestris wrote:
>> Hello,
>>
>> I'm not sure we can accept only one connection at a given time. I
>> tested with the "prefork MPM", and I only achieve 1 concurrent
>> request
On 19/02/16, Aurélien Terrestris wrote:
> Hello,
>
> I'm not sure we can accept only one connection at a given time.
> I tested with the "prefork MPM", and I only achieve 1 concurrent request
> being processed at a given time and all others requests are buffered
> (ListenBackLog doesn't seem to wo
On 19/02/16, Richard wrote:
>
>
> > Date: Friday, February 19, 2016 13:32:02 +0100
> > From: Oliver Graute
> >
> > On 19/02/16, Jim Jagielski wrote:
> >> Just one connection? By that do you mean one concurrent user or
> >> actually one request or actually one connection?
> >>
> >> A connection
Jim,
-X stops with a seg-fault after servicing the request, at least on my
server. I suppose that we need to keep the server alive.
2016-02-19 14:02 GMT+01:00 Dr James Smith :
> Can you not just go into debug mode -X?
>
>
>
> On 19/02/2016 12:52, Aurélien Terrestris wrote:
>
> Richard, is th
On Fri, Feb 19, 2016 at 1:32 PM, Oliver Graute wrote:
>
> my requirement is:
>
> "The Apache server listens on port 443i (https). It must accept only one
> connection at a time on this port"
>
> so its one socket opened between the client and the server.
I guess "ServerLimit 1" would do it (alon
Can you not just go into debug mode -X?
On 19/02/2016 12:52, Aurélien Terrestris wrote:
Richard, is this a config that you tried successfully ? On my server,
"prefork MPM" will put requests in the backlog (waiting), and "event
MPM" is not designed for such behaviours because of its
multi-thre
Yeah...
No idea why anyone in the world would do this though...
> On Feb 19, 2016, at 7:46 AM, Richard
> wrote:
>
>
>
>> Date: Friday, February 19, 2016 13:32:02 +0100
>> From: Oliver Graute
>>
>> On 19/02/16, Jim Jagielski wrote:
>>> Just one connection? By that do you mean one concurrent
Richard, is this a config that you tried successfully ? On my server,
"prefork MPM" will put requests in the backlog (waiting), and "event MPM"
is not designed for such behaviours because of its multi-threading model (I
did not try "hybrid MPM" since it is supposed to be multi-threaded as well)
> Date: Friday, February 19, 2016 13:32:02 +0100
> From: Oliver Graute
>
> On 19/02/16, Jim Jagielski wrote:
>> Just one connection? By that do you mean one concurrent user or
>> actually one request or actually one connection?
>>
>> A connection is a socket opened between the client and the se
Hello,
I'm not sure we can accept only one connection at a given time.
I tested with the "prefork MPM", and I only achieve 1 concurrent request
being processed at a given time and all others requests are buffered
(ListenBackLog doesn't seem to work on my server). Once the 1st request has
been proc
On 19/02/16, Jim Jagielski wrote:
> Just one connection? By that do you mean one concurrent user or
> actually one request or actually one connection?
>
> A connection is a socket opened between the client and the server.
> A request is a HTTP request on that connection.
my requirement is:
"The
Just one connection? By that do you mean one concurrent user or
actually one request or actually one connection?
A connection is a socket opened between the client and the server.
A request is a HTTP request on that connection.
tia.
> On Feb 19, 2016, at 2:50 AM, Oliver Graute wrote:
>
> On 18/
On 18/02/16, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Oliver,
>
> On 2/18/16 8:31 AM, Oliver Graute wrote:
> > is it possible to configure Apache 2.4 to accept only one
> > connection at time on port 443? is this something I can configure
> > for my Virtual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oliver,
On 2/18/16 8:31 AM, Oliver Graute wrote:
> is it possible to configure Apache 2.4 to accept only one
> connection at time on port 443? is this something I can configure
> for my Virtual Hosts?
For testing, or for long-term behavior?
- -chris
Hello,
is it possible to configure Apache 2.4 to accept only one connection at
time on port 443? is this something I can configure for my Virtual Hosts?
Best regards,
Oliver
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apa
19 matches
Mail list logo
