[Info-vax] Apache + mod_php performance

[Arne Vajhøj]

On 10/1/2024 7:55 PM, Dan Cross wrote:
> In article <66fc58ce$0$708$14726298 at news.sunsite.dk>,
> Arne Vajhøj  <arne at vajhoej.dk> wrote:
>> On 10/1/2024 3:45 PM, Dan Cross wrote:
>>> In article <vd9mqn$1cm1v$1 at dont-email.me>,
>>> Dave Froble  <davef at tsoft-inc.com> wrote:
>>>> On 9/27/2024 9:11 PM, Arne Vajhøj wrote:
>>>> [snip]
>>>>> I believe that server config supporting keep alive
>>>>> causing performance to drop to 1/10'th for clients
>>>>> not using keep alive is a bug.
>>>>
>>>> Feature ...
>>>
>>> Yes, it is a feature, despite this report of a non-problem.
>>>
>>> In this case, later posts revealed the real culprit: Arne's test
>>> program did not follow the protocol, and was not sending
>>> `Connection: close` with an HTTP/1.1 request; in response, the
>>> server (correctly) kept the connection open waiting for the
>>> client to send another request.
>>
>> It does not really make any sense for the test client
>> to send "Connection: close".
> 
> It makes even less sense to implement the protocol improperly
> and then blame the other side when it doesn't work the way you
> expect, wouldn't you agree?

Not sending "Connection: close" header is perfectly valid.
And it is the normal scenario.

Sending "Connection: close" with every request is the client
way to disable keep alive. And the unusual scenario.

Disabling keep alive client side not surprisingly has
the same effect as disabling keep alive server side.

But while disabling keep alive server side makes sense
then it doesn't make sense to disable it client side.

Arne