The problem was first discovered with Apache 2.4.18 compiled against
OpenSSL/1.0.1m. The running system, which is an i686 Linux system, used
the same versions.
We then installed our old mod_ssl.so from Apache 2.4.12, everything else
unchanged, and this worked. This was enough of a hint to debug the
2.4.18 version of the module. Before doing this, we downloaded the
latest apr/apr-util, and OpenSSL packages, and rebuilt everything.
OpenSSL is now at 1.0.2f. All of this was installed on the running
system, and it behaved the same way, with some files causing the client
to hang forever.
Applying the patch I included in the previous message gets it working
for us.
Joachim
On 2016-02-01 12:06 AM, Yann Ylavic wrote:
On Mon, Feb 1, 2016 at 3:41 AM, Joachim Achtzehnter <joac...@kraut.ca> wrote:
After upgrading from 2.4.12 to 2.4.18 we find that some requests for files
cause a lock-up when HTTPS is used, but not with plain HTTP. After some
debugging it seems the problem is that the mod_ssl no longer explicitly
flushes the output it produced before going back to reading a new request on
the same connection.
This is a 32-bit Intel Linux platform, and by stepping through the mod_ssl
output filter in the debugger I can see that the files that cause problems
are being read by Apache using the mmap approach.
Restoring the explicit flushing from 2.4.12 gets the 2.4.18 version of
mod-ssl working for us. Here is the patch:
Which system and openssl versions are you using?
Did you build 2.4.18 yourself, against the same version of openssl the
system is running?
Regards,
Yann.
--
joac...@kraut.ca www.kraut.ca
