On Tue, Jul 11, 2017 at 9:13 AM, Hajo Locke wrote:
>
> Am 11.07.2017 um 15:58 schrieb Eric Covener:
>>
>> On Tue, Jul 11, 2017 at 9:41 AM, David Copeland
>> wrote:
o HTTP/2 will not be negotiated when using the Prefork MPM
>>>
>>> I'm wondering what the reason for this is?
>>
>> In the
Hello,
Am 11.07.2017 um 16:08 schrieb David Copeland:
On 11/07/17 09:58 AM, Eric Covener wrote:
On Tue, Jul 11, 2017 at 9:41 AM, David Copeland
wrote:
o HTTP/2 will not be negotiated when using the Prefork MPM
I'm wondering what the reason for this is?
In the previous release, HTTP2 made pr
On 11/07/17 10:25 AM, Stefan Eissing wrote:
>> Am 11.07.2017 um 16:13 schrieb David Copeland :
>>
>> I had it set up on an essentially a private site to try it so the volume was
>> very low, and so I never had a problem.
> It can work in certain configurations. Especially if you *only* serve stati
> Am 11.07.2017 um 16:13 schrieb David Copeland :
>
> I had it set up on an essentially a private site to try it so the volume was
> very low, and so I never had a problem.
It can work in certain configurations. Especially if you *only* serve static
files. As soon as mod_php, proxy connections
On 11/07/17 09:58 AM, Eric Covener wrote:
> On Tue, Jul 11, 2017 at 9:41 AM, David Copeland
> wrote:
>>> o HTTP/2 will not be negotiated when using the Prefork MPM
>> I'm wondering what the reason for this is?
> In the previous release, HTTP2 made prefork run multi-threaded. People
> often chose p
I had it set up on an essentially a private site to try it so the volume
was very low, and so I never had a problem.
Thanks,
Dave Copeland.
On 11/07/17 10:03 AM, Yehuda Katz wrote:
> H2 is threaded and prefork is not, so the performance is poor or it
> doesn't work at all.
>
> There was a discuss
Hello,
Am 11.07.2017 um 15:58 schrieb Eric Covener:
On Tue, Jul 11, 2017 at 9:41 AM, David Copeland
wrote:
o HTTP/2 will not be negotiated when using the Prefork MPM
I'm wondering what the reason for this is?
In the previous release, HTTP2 made prefork run multi-threaded. People
often chose
Also a more in depth explanation from the dev@ mailing list:
https://lists.apache.org/thread.html/bae472cadaeeb761b88bb4569cc0b7d87bc2dcb2fbcbf472d895f32e@%3Cdev.httpd.apache.org%3E
Luca
2017-07-11 15:56 GMT+02:00 Luca Toscano :
> Hi David,
>
> https://bz.apache.org/bugzilla/show_bug.cgi?id=612
H2 is threaded and prefork is not, so the performance is poor or it doesn't
work at all.
There was a discussion about this on the dev list:
https://lists.apache.org/thread.html/bae472cadaeeb761b88bb4569cc0b7d87bc2dcb2fbcbf472d895f32e@%3Cdev.httpd.apache.org%3E
Sent from a device with a very small
Hi David,
https://bz.apache.org/bugzilla/show_bug.cgi?id=61237 contains the
background that brought to this decision :)
Luca
2017-07-11 15:41 GMT+02:00 David Copeland :
> I'm wondering what the reason for this is?
>
> Thanks.
>
> On 11/07/17 09:04 AM, Jim Jagielski wrote:
> >Apache
On Tue, Jul 11, 2017 at 9:41 AM, David Copeland
wrote:
>> o HTTP/2 will not be negotiated when using the Prefork MPM
> I'm wondering what the reason for this is?
In the previous release, HTTP2 made prefork run multi-threaded. People
often chose prefork due to non-threadsafe code running in the se
I'm wondering what the reason for this is?
Thanks.
On 11/07/17 09:04 AM, Jim Jagielski wrote:
>Apache HTTP Server 2.4.27 Released
>
>
> o HTTP/2 will not be negotiated when using the Prefork MPM
>
--
David Copeland
JSI Data Systems Limited
613-727-9353
www.jsidata.ca
-
Apache HTTP Server 2.4.27 Released
July 11, 2017
The Apache Software Foundation and the Apache HTTP Server Project
are pleased to announce the release of version 2.4.27 of the Apache
HTTP Server ("Apache"). This version of Apache is our latest GA
release of the new generation 2.4.x br
13 matches
Mail list logo
