I'm running (trying to run, actually) Apache 2.4.2 on Windows Server 2003 R2 32 bit (plus PHP 5.4.5 and OpenSSL 1.0.1c, but I don't think that matters), and I'm getting the following line in the error log:
[Sun Aug 05 11:52:39.546875 2012] [ssl:warn] [pid 5712:tid 348] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
Trying to connect to https://localhost/ gets a 102 – Connection refused error.
What puzzles me is that SSLSessionCache is configured:
SSLSessionCache "shmcb:C:/Program Files/Apache Software Foundation/Apache2.4/logs/ssl_scache(512000)"
It's exactly the same line of the configuration file I had for Apache 2.2.17 (except for /Apache2.2 instead of 2.4), which runs just fine. Using mod_status, I'm getting no informations for "SSL/TLS Session Cache Status", while I do for Apache 2.2.
I don't think there are many differences between the two httpd-ssl.conf files, mainly between paths, but it seems they're all right.
The virtual server on port 80 runs okay.
What am I missing?
Edit: for those who are wondering, this isn't the misleading warning that someone got when the machine couldn't resolve the ServerName. Apache 2.2 has no problem with it, and I even flushed the DNS cache with netstat /flushdns.
Best Answer
The culprit wasn't found in http-ssl.conf, but in httpd.conf.
I suspected that when I saw that the server status wasn't reporting the "SSL/TLS Session Cache Status" section at all, rather than an empty section. It happened that the
Includedirective in httpd.conf pointed to an old test .conf file instead of httpd-ssl.conf.Well, duh! This may help other newbies like me in the future...