On Wed, Jan 23, 2019 at 09:37:46PM +0100, Aleksandar Lazic wrote:
>
> Am 23.01.2019 um 21:27 schrieb Willy Tarreau:
> > On Wed, Jan 23, 2019 at 09:08:00PM +0100, Aleksandar Lazic wrote:
> >> Should it be possible to have fe with h1 and be server h2(alpn h2), as I
> >> expect this or similar return value when I go thru haproxy?
> >
> > Yes absolutely. That's even what I'm doing on my tests to try to fix
> > the issues reported by Luke.
>
> Okay, perfect.
>
> Would you like to share your config so that I can see what's wrong with my
> config, thanks.
Sure, here's a copy-paste, hoping I don't mess with anything :-)
defaults
mode http
option http-use-htx
option httplog
log stdout format raw daemon
timeout connect 4s
timeout client 10s
timeout server 10s
frontend decrypt
bind :4445
bind :4446 proto h2
bind :4443 ssl crt rsa+dh2048.pem npn h2 alpn h2
default_backend trace
backend trace
stats uri /stat
server s1 127.0.0.1:443 ssl alpn h2 verify none
#server s2 127.0.0.1:80
#server s3 127.0.0.1:80 proto h2
As you can see you just connect to port 4445.
> >> I haven't seen any log option to get the backend request method, I think
> >> this
> >> should be a feature request ;-).
> >
> > What do you mean with "backend request method" precisely ?
>
> As the log is for frontends It would be nice to be able to get this infos
> from below also for the backend to see what was send to the backend server.
But what is sent to the backend is what comes from the frontend. And there
never is any valid reason for rewriting the method. So the method sent to
the backend is *always* what you receive on the fronend.
Cheers,
Willy
