I just enabled http2 on our server and tested using curl. The test page is a static html page with nothing but some random characters on it, and no css or other secondary accesses. The protocol line is set to allow http2 Protocols h2 h2c http/1.1 Everything seems to work with the exception of the date. The first file following is the result of a curl head request BEFORE activating mod_http2 and the second one is after doing so. No other change to the httpd.conf file. ---------------------without http2 being available---------------------- curl --http2 -I http://192.168.1.6:/yrarc/yrex0001.html HTTP/1.1 200 OK Date: Fri, 07 Apr 2017 03:42:12 GMT <----- Server: Apache X-Frame-Options: SAMEORIGIN Last-Modified: Sun, 26 Mar 2017 03:12:45 GMT ETag: "c14-54b9999bf581b" Accept-Ranges: bytes Content-Length: 3092 Content-Type: text/html -------------------with mod_http2 enabled------------------------------ curl --http2 -I http://192.168.1.6:/yrarc/yrex0001.html HTTP/1.1 101 Switching Protocols Upgrade: h2c Connection: Upgrade HTTP/2 200 date: Sun, 00 Jan 1900 00:00:00 GMT <----- server: Apache x-frame-options: SAMEORIGIN last-modified: Sun, 26 Mar 2017 03:12:45 GMT etag: W/"c14-54b9999bf581b" accept-ranges: bytes content-length: 3092 content-type: text/html Does anyone know why the date (arrowed) should be wrong and if it would make any difference in the server operation? Or maybe what am I missing? Thanks. John ===================================== --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|