Quantcast
Channel: HAProxy community - Latest topics
Viewing all articles
Browse latest Browse all 4750

Bind "name" parameter seems to be ignored

$
0
0

@sottolski wrote:

Howdy,

I'm trying to condense my configruation for 1.6.6 a bit. Instead of

frontend FE-1
    bind 172.17.1.11:443 ssl crt /etc/ssl/private/mycert.pem
    reqadd "X-Forwarded-Proto: https"
    default_backend app-servers

frontend FE-2
    bind 172.17.1.12:443 ssl crt /etc/ssl/private/mycert.pem
    reqadd "X-Forwarded-Proto: https"
    default_backend app-servers

frontend FE-3
    bind 172.17.1.13:443 ssl crt /etc/ssl/private/mycert.pem
    reqadd "X-Forwarded-Proto: https"
    default_backend app-servers

I thought I could do something like

frontend SSL
    bind 172.17.1.11:443 ssl crt /etc/ssl/private/mycert.pem name FE-1
    bind 172.17.1.12:443 ssl crt /etc/ssl/private/mycert.pem name FE-2
    bind 172.17.1.13:443 ssl crt /etc/ssl/private/mycert.pem name FE-3
    reqadd "X-Forwarded-Proto: https"
    default_backend app-servers

The docs tell me

name

<name>

Sets an optional name for these sockets, which will be reported on the stats
page.

However, I seem not the see any of may names on the stats page.

Is it a misunderstanding on my side what the name is for, or may it be a bug?

Thanks

Sascha

Posts: 1

Participants: 1

Read full topic


Viewing all articles
Browse latest Browse all 4750

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>