Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
From: John Iliffe <john.iliffe@iliffe.ca>
To: users@httpd.apache.org
Date: Fri, 7 Apr 2017 11:28:06 -0400
User-Agent: KMail/1.13.3 (Linux/2.6.33.7-desktop-2mnb; KDE/4.4.3; x86_64; ; )
References: <201704070019.52837.john.iliffe@iliffe.ca> <CABzHfVnkGX1G+ADRXyWQSTYDPVtQKodA4EuzPPmU0zucNLS6mQ@mail.gmail.com>
In-Reply-To: <CABzHfVnkGX1G+ADRXyWQSTYDPVtQKodA4EuzPPmU0zucNLS6mQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201704071128.06861.john.iliffe@iliffe.ca>
Subject: Re: [users@httpd] Odd Date in http2 header
archived-at: Fri, 07 Apr 2017 15:20:29 -0000

On Friday 07 April 2017 03:53:55 Konstantin Kolinko wrote:
> 2017-04-07 7:19 GMT+03:00 John Iliffe <john.iliffe@iliffe.ca>:
> > 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?
> 
> 1. What is exact version of your server?

apache-2.4.25 compiled from source running on Fedora 25
> 
> 2. If you say that "No other change to the httpd.conf file", what
> caused the difference in ETag value?
Don't know, the "W/" bit occurs only when the http2 protocol is active.

The only change I made was to uncomment the line: 

LoadModule http2_module modules/mod_http2.so

the Protocol line was already present, but as noted in the docs ignores 
protocols that are not available.
> 
> 3. Overall, this is strange.
> If you do an HTTP/1.1 request (using curl without "--http2" flag),
> does it respond with a correct Date header?
Yes.

curl -I http://192.168.1.6:/yrarc/yrex0001.html
HTTP/1.1 200 OK
Date: Fri, 07 Apr 2017 15:07:47 GMT      <--------
Server: Apache
X-Frame-Options: SAMEORIGIN
Upgrade: h2,h2c
Connection: Upgrade
Last-Modified: Sun, 26 Mar 2017 03:12:45 GMT
ETag: "c14-54b9999bf581b"
Accept-Ranges: bytes
Content-Length: 3092
Content-Type: text/html
> 
> 4. I wonder, whether the behaviour is affected by H2SerializeHeaders
> directive.
> http://httpd.apache.org/docs/2.4/mod/mod_http2.html#h2serializeheaders
Bingo!

The H2SerializeHeaders directive is not present so it is taking the default 
of off.  I added it with the following result:

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: Fri, 07 Apr 2017 15:16:38 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

> 
So, what is this dated used for and does an incorrect date affect anything?  
The docs sort of imply that it should be off unless something breaks.
> Best regards,
> Konstantin Kolinko
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org