Hi Pieter,
I'm finally back to this one.
On Sat, Jan 26, 2019 at 09:04:06PM +0100, PiBa-NL wrote:
> It seems google replies "Header: :status: 400 Bad Request" But leaves me
> 'guessing' why it would be invalid, also the 'body' doesn't get downloaded
> but haproxy terminates the connection, which curl then reports as missing
> bytes.. There are a few differences between the 2 get requests, authority
> and scheme.. But i also wonder if that is the actual packet with the issue,
> H2 isnt quite a simple as H1 used to be ;).
I didn't manage to get your vtc to work because I think they were mangled
during your multiple attempts (e.g. some are in TCP mode). However I could
come up with a trivial config that used to fail and which now works after
I patched the code :
global
tune.ssl.default-dh-param 1024
listen proxy
mode http
option http-use-htx
timeout connect 20s
timeout client 20s
timeout server 20s
log stdout format raw local0
option httplog
bind :4445
bind :4446 proto h2
server srv_mailgoogle mail.google.com:443 ssl verify none alpn h2
$ curl -i --http2-prior-knowledge http://127.0.0.1:4446/mail/ -H "Host:
mail.google.com"
Now we get the proper redirect instead of the 400 bad req.
I've mergd this into master and the pending 1.9. Feel free to give it
a try.
cheers,
Willy
