Chris,
http://freebsd-admin.com does a 302 redirect to https://freebsd-admin.com
There is no connection upgrade happening on that. Can be argued that it should.
On the https side, I see:
* Connected to freebsd-admin.com (78.46.185.201) port 443 (#0)
* ALPN, offering h2
* ALPN, offering
yep the redirect is deliberate, its actually a site I only use in https.
The server in question has directadmin control panel, which configures
the vhosts via templates.
I added the protocols line at the start of the vhost so it is right at
the start of the vhost container above servername etc.
Ok stefan I have some good news, it is working on another vhost on
both http and https, this is odd as the server config is the same and
vhost templates match, will post more if I find out why the first
vhost fails.
Thanks
On 16 October 2015 at 11:23, Chris wrote:
> some
some more configure info
# httpd -V
Server version: Apache/2.4.17 (Unix)
Server built: Oct 16 2015 08:46:36
Server's Module Magic Number: 20120211:51
Server loaded: APR 1.5.2, APR-UTIL 1.5.4
Compiled using: APR 1.5.2, APR-UTIL 1.5.4
Architecture: 64-bit
Server MPM: event
threaded:
Sorry I meant I tried using Protocols h2 not g2 that was a typo.
On 16 October 2015 at 10:48, Stefan Eissing
wrote:
>
> Chris,
>
> http://freebsd-admin.com does a 302 redirect to https://freebsd-admin.com
>
> There is no connection upgrade happening on that. Can be
Well I am left scratching my head, the first vhost now works ok on
https using curl as a tester, nghttp seems ok as well, although my
output isnt the same as your document.
I think you was right that the 302 redirect was breaking it on the
http vhost as that still doesnt work but both http and
Thanks! Yeah, h2check.org is not working properly, it has not been updated for
some time.
I'll add a line about 302 h2c upgrades not working in the howto...
> Am 16.10.2015 um 13:02 schrieb Chris :
>
> Well I am left scratching my head, the first vhost now works ok on
>