Thanks for the response Stefan. Much appreciated.
The following results are from a vhost with the following configuration;
just the default vhost on a named virtual host system.
This is in the main server configuration and is REQUIRED by the e-commerce
folks (PCIA) to get a clean scan report
Hmm, interesting. I left H2SerializeHeaders in just for the case someone
runs into incompatibilities with the standard mod_http2 method. I almost
was about to rip it our since, until now, no one reported any differences.
I'd like to understand what is going on in your system and causing this
On Friday 07 April 2017 03:53:55 Konstantin Kolinko wrote:
> 2017-04-07 7:19 GMT+03:00 John Iliffe :
> > 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
2017-04-07 7:19 GMT+03:00 John Iliffe :
> 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
>
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