大网数据广告活动
服务器运维问答

haproxy logging of req.ssl_sni

· 52CE 我爱测

I am trying to extend a custom haproxy log-format by adding [req.ssl_sni]. The haproxy version used is 1.6.3 on Ubuntu. The frontend is configured in the following way: bind *:443 mode tcp tcp-request inspect-delay 5s tcp-request…

问题原文

原帖链接 · Cybran · CC BY-SA 3.0

I am trying to extend a custom haproxy log-format by adding [req.ssl_sni]. The haproxy version used is 1.6.3 on Ubuntu.

The frontend is configured in the following way:

bind *:443
mode tcp

tcp-request inspect-delay 5s
tcp-request content accept if { req_ssl_hello_type 1 }
tcp-request content reject

log-format [...]{%[req.ssl_sni]}

Where [...] denotes other log options which are working fine. The frontend is running in TCP mode, forwarding TLS sessions without decrypting them.

The expected log output would be something similar to {my.server.com} for valid TLS sessions. The log output I am seeing is always {-} (a dash instead of the server name), even when the TLS session is successfully handled by the backend server. What do I have to change to see the actual SNI value in the logs?

已采纳解答

原帖链接 · DTT · CC BY-SA 4.0

Using capture before accept solved it for me.

frontend https-in
  mode tcp
  tcp-request inspect-delay 3s
  tcp-request content capture req.ssl_sni len 10
  log-format "capture0: %[capture.req.hdr(0)]"
  tcp-request content accept if { req_ssl_hello_type 1 }
  use_backend test_0 if req.ssl_sni -m end /test

Found solution in here: https://discourse.haproxy.org/t/log-sni-in-tcp-mode/1534/2

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-12-20)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0 / CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。