WampServer

I don't think HTTP2 is working correctly on my WampServer Apache web server. The problem I'm having is that Chrome Dev Tools reports queueing after every h2 download, which I wouldn't expect for the HTTP2 protocol. Even though Dev Tools reports "h2" for the protocol for each downloaded element, the queueing matches exactly what I see when I use HTTP 1.1. My hosted web sites use HTTP2 and I don't see any queueing in Chrome Dev Tools for those sites. My suspicion is that my WampServer HTTP2 configuration isn't correct.

I'm running WampServer 3.2.2. I've updated Apache to 2.4.43a. When I click the WampServer tray icon, hover over "Apache" then hover over "Apache modules" the http2_module doesn't have a green check mark, even though it is enabled in httpd.conf.

I've read the Apache documentation about enabling HTTP2 and I suspect that I don't have something configured correctly between my SSL (I have enabled the ssl_module and it has a green check mark and my websites can get to localhost using https) and the http2_module. Can someone point me to information about how to "connect" the Apache http2_module to my SSL environment?

If you think my problem is something other than an SSL issue, please let me know.

Thanks In Advance!

Hi,

> WampServer 3.2.2.
Update to 3.2.7 **

> I've updated Apache to 2.4.43a.
Update to 2.4.52
How to enable SSL in Wampserver

With all this, http 2 works fine.
Maybe you shouldn't trust Chrome Dev Tools!
Apache access.log shows that http2 is active.

::1 - - [13/Feb/2022:09:58:57 +0100] "GET /css/general.css HTTP/2.0" 304 -
::1 - - [13/Feb/2022:09:58:57 +0100] "GET /images/crevette1.png HTTP/2.0" 304 -
::1 - - [13/Feb/2022:09:58:57 +0100] "GET /images/superstarliner150.jpg HTTP/2.0" 304 -
::1 - - [13/Feb/2022:09:58:57 +0100] "GET /images/bimoteur150.jpg HTTP/2.0" 304 -
::1 - - [13/Feb/2022:10:00:15 +0100] "GET /vilgenis/vilgenis.php HTTP/2.0" 200 16223
::1 - - [13/Feb/2022:10:00:15 +0100] "GET /css/unites.css HTTP/2.0" 200 2824
::1 - - [13/Feb/2022:10:00:15 +0100] "GET /vilgenis/images/mini/plaque_grille.jpg HTTP/2.0" 200 15061

I'm not an expert on Apache configuration, but what I observe is that http2 goes with IPv6.
In the Apache logs, I don't have any http2 with IPv4. You may need to verify that IPv6 is enabled on your system.

** Before launching the Wampserver 3.2.7 update, verify that all VC ++ packages are installed and with the latest versions.
To do this, use the tool:
Checks VC++ packages installed
Do not use a previously loaded tool. Make a new download to make sure you are using the correct version.[/u)
To download missing packages, do not rely on Microsoft links, they are not reliable, download packages on http://wampserver.aviatechno.net in section Visual C++ Redistribuable Packages
Do not forget that if you have a 64 bit Windows, you must install both 32 and 64 bit versions of each package.
You must install each package "as an administrator", so right-click the exe file and then run as Administrator.

> http2_module doesn't have a green check mark
Try:
Right-Click -> Tools -> Empty logs -> Empty all logs -> Y

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons



Edited 2 time(s). Last edit at 02/13/2022 12:19PM by Otomatic.

Thanks, Otomatic, for the reply. I didn't think to check the Apache access logs. When I did, everything was being accessed using HTTP2. Thanks for reminding me to do that!

My original problem still remains - Why is there queueing on the Chrome Dev Tools "Network" tab Waterfall graph for HTTP2 requests? I realize this problem may be outside the scope of this forum. :>

Hi,

First, did you read the full spec for HTTP2, its configureation is not just a case of enabling the module.

Second, did you compare these results using some other browsers, FF, Edge.
HTTP/2 means that more assets can be downloaded at once - not that they will be. Browsers have various heuristics as to what to download and when.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Hi Riggs. Yes, I checked the Apache documentation regarding HTTP2. I didn't understand everything I was reading, so I opened a support ticket on this forum hoping that somebody had made the use of the Apache HTTP2 directives clearer.

After additional testing today, the issue with HTTP2 queueing turns out to be a configuration issue in one of the WordPress core files I have modified to report various browser characteristics. From what is being reported in the Apache logs, and what I see as the Protocol value in Chrome Dev Tools ("h2", which is HTTPS using HTTP2), I'm comfortable that HTTP2 is the protocol that is being used by the client to connect with my WampServer Apache web server.

I'm assuming the lack of a green checkmark in the WampServer Apache 2.4.43a modules listing is a bug and that HTTP2 is working correctly?

Hi,

> I'm assuming the lack of a green checkmark in the WampServer Apache.....

If, in httpd.conf there is

LoadModule http2_module modules/mod_http2.so

with no hash (#) at the beginning, there should be a green checkmark to the left of http2_module in the menu Click-Left -> Apache -> Apache modules

Have you done what I recommended in a previous post?

Right-click -> Tools -> Empty logs -> Empty all log files -> Y
then
Right-click -> Refresh

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

Otomatic, I right-clicked the WampServer icon in the system tray, clicked Tools > Miscellaneous > Empty logs > Empty Apache access log. A CMD window opened asking if I wanted to clear the log file located at:

C:\WAMP64\logs\access.log. I answered "Y" and the log was cleared.

However, the Apache access log that is being updated is located at:

C:\WAMP64\bin\apache\apache2.4.43a\logs\access.log

Why doesn't WampServer point to the \apache2.4.43a\logs\access log? Is that because I have updated the original Apache that was installed with WampServer? How can I fix this?

Hi,

All log files are in the folder wamp(64)/logs/

 Le volume dans le lecteur E s'appelle SATA_1_E
 Le numéro de série du volume est F491-4AA3

 Répertoire de E:\wamp64\logs

14/02/2022  14:33    <DIR>          .
14/02/2022  14:33    <DIR>          ..
14/02/2022  18:57            78 886 access.log
14/02/2022  18:58           100 024 apache_error.log
14/02/2022  09:26            22 089 custom.log
08/02/2022  17:52                64 error.log
14/02/2022  18:58            40 504 mariadb.log
14/02/2022  18:58            18 928 mysql.log
14/02/2022  18:33                 0 php_error.log
19/09/2019  09:11                62 wamptrace.log
08/02/2022  17:52                64 xdebug.log
               9 fichier(s)          260 621 octets
               2 Rép(s)  91 555 196 928 octets libres

This is done by the different configuration files:
- Apache - httpd.conf
ErrorLog "${INSTALL_DIR}/logs/apache_error.log"
CustomLog "${INSTALL_DIR}/logs/access.log" common
- PHP - php.ini phpForApache.ini
error_log ="E:/wamp64/logs/php_error.log"
xdebug.log="E:/wamp64/logs/xdebug.log"
- MySQL - my.ini
log-error="E:/wamp64/logs/mysql.log"
- MariaDB - my.ini
log-error="E:/wamp64/logs/mariadb.log"

> Why doesn't WampServer point to the \apache2.4.43a\logs\access log?
Because you have modified or added log file definitions, for example in VirtualHost as indicated in the httpd.conf file:

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

So, I found this in my httpd-ssl.conf file:

#   General setup for the virtual host
#(ORIGINAL) DocumentRoot "${SRVROOT}/htdocs"
DocumentRoot "c:/WAMP64/www/"
#(ORIGINAL) ServerName www.example.com:443
ServerName localhost:443
ServerAdmin admin@example.com
ErrorLog "${SRVROOT}/logs/error.log"
TransferLog "${SRVROOT}/logs/access.log"

Is this what is changing the path to the Apache access.log file? If this is the case, then reviewing the access.log file located in the \logs folder in the root of my Apache installation would be the correct place to confirm that HTTP2 was being used, correct?



Edited 1 time(s). Last edit at 02/16/2022 02:13PM by RiggsFolly.

Hi,

> ErrorLog "${SRVROOT}/logs/error.log"
You have to check the Define directives in httpd.conf plus a little passage through the Apache documentation
Define

Nevertheless, what I asked you to do is: Empty ALL log files and not only apache access.log

As for http2, see the official http2 protocol guide:
HTTP/2 guide

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

I emptied all log files by following your instructions. All of the log files located at C:\WAMP64\logs became 0 bytes. I launched localhost and refreshed the browser several times. None of the log files at C:\WAMP64\logs were updated.

I checked for the definition of logfiles in httpd.conf and discovered the following statement:

CustomLog "${INSTALL_DIR}/logs/access.log" common

I also checked httpd-ssl.conf and found the following statement (which I reported in a previous post):

TransferLog "${SRVROOT}/logs/access.log"

After reading the Apache help files regarding the configuration of log files I believe it is these two statements that are causing Apache to update the access.log file that is located in the Apache install root at \logs.

Am I understanding all of this correctly?

Hi,

You have to look for yourself and see what the contents of the Apache variables are, in other words see where they are defined!
I've even told you where to find the documentation for the Apache Define directive!

httpd.conf file

Define APACHE24 Apache2.4
Define VERSION_APACHE 2.4.52a
Define INSTALL_DIR E:/wamp64
Define APACHE_DIR ${INSTALL_DIR}/bin/apache/apache${VERSION_APACHE}
Define SRVROOT ${INSTALL_DIR}/bin/apache/apache${VERSION_APACHE}

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons