Perhaps sharing this on the dev-list will allow the people who actually
implemented this new default to take a look:
-- Forwarded message --
From: Mathijs
Date: Sat, Feb 18, 2012 at 8:42 PM
Subject: Documentation of MaxConnectionsPerChild default value
To: d...@httpd.apache.org
Ok, issues with all mod_ssl would be a big problem.
If you needed to do DisableWin32AcceptEx, though, then something was
already not quite right.
What you mean by "mod_ssl on a port", though? You just mean running an
HTTPS listener right?
On 2/18/2012 12:43 AM, William A. Rowe Jr. wrote:
On 2/19/2012 9:56 PM, William A. Rowe Jr. wrote:
> From this link; http://httpd.apache.org/docs/2.4/ you will observe
> that the lower half of the right column is the 'official' place for
> platform/architecture docs. Outright bugs should be corrected by
> offering a patch.
So far this documentat
On 20 Feb 2012, at 5:16 PM, Daniel Ruggeri wrote:
> Agreed - the wiki is the place to create these types of docs and let
> packagers and maintainers tweak/enhance them until maturity. I've been
> building on AIX for years and was pleased to learn something new from
> Eric's article you mentioned.
patch (and patch file name) says it all
Index: Announcement2.4.html
===
--- Announcement2.4.html(revision 501)
+++ Announcement2.4.html(working copy)
@@ -20,14 +20,25 @@
The Apache Software Foundation and the Apac
On Mon, Feb 20, 2012 at 8:47 PM, Jeff Trawick wrote:
> patch (and patch file name) says it all
+1
Looks fine to me... Will fold in.
On Feb 20, 2012, at 8:47 PM, Jeff Trawick wrote:
> patch (and patch file name) says it all
>
On 2/20/2012 8:04 AM, Jess Holle wrote:
> Ok, issues with all mod_ssl would be a big problem.
>
> If you needed to do DisableWin32AcceptEx, though, then something was already
> not quite right.
>
> What you mean by "mod_ssl on a port", though? You just mean running an HTTPS
> listener right?
On 2/20/2012 9:16 AM, Daniel Ruggeri wrote:
>
> So far this documentation doesn't seem to deal with build activities
> which is where the conversation has grown... I'm not sure it should.
I disagree. I wrote paragraphs of build docs for more than one platform.
If the docs need to improve, let's