cloud-hosting-platform/haproxy-manager-base
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix table reference and log-format response header issues
All checks were successful
HAProxy Manager Build and Push / Build-and-Push (push) Successful in 54s
Details

Browse Source 
- Remove reference to non-existent security_blacklist table
- Use single table tracking with consolidated array-based GPC system
- Remove res.hdr(X-Threat-Level) from log-format as response headers not available in request phase
- Maintains threat intelligence logging with available request-phase data

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
jknapp
2025-09-22 18:49:50 -07:00
parent b293588eef
commit 4c4e99883b
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
templates/hap_listener.tpl
View File

@@ -79,9 +79,8 @@ frontend web
http-request set-var(txn.real_ip) req.hdr(X-Forwarded-For) if !has_cf_connecting_ip !has_x_real_ip has_x_forwarded_for http-request set-var(txn.real_ip) req.hdr(X-Forwarded-For) if !has_cf_connecting_ip !has_x_real_ip has_x_forwarded_for
http-request set-var(txn.real_ip) src if !has_cf_connecting_ip !has_x_real_ip !has_x_forwarded_for http-request set-var(txn.real_ip) src if !has_cf_connecting_ip !has_x_real_ip !has_x_forwarded_for
# Multi-table tracking for comprehensive security monitoring # Single table tracking for comprehensive security monitoring
http-request track-sc0 var(txn.real_ip) http-request track-sc0 var(txn.real_ip)
http-request track-sc1 var(txn.real_ip) table security_blacklist
# ============================================ # ============================================
# APPLY SECURITY RULES # APPLY SECURITY RULES
@@ -214,7 +213,7 @@ frontend web
http-request capture var(txn.threat_score) len 10 http-request capture var(txn.threat_score) len 10
# Enhanced logging format with glitch information # Enhanced logging format with glitch information
log-format "%{+json}o %(client_ip)[var(txn.real_ip)] %(threat_score)[var(txn.threat_score)] %(glitches)[fc_glitches] %(h2_streams)[fc_nb_streams] %(user_agent)[capture.req.hdr(1)] %(threat_level)[res.hdr(X-Threat-Level)]" log-format "%{+json}o %(client_ip)[var(txn.real_ip)] %(threat_score)[var(txn.threat_score)] %(glitches)[fc_glitches] %(h2_streams)[fc_nb_streams] %(user_agent)[capture.req.hdr(1)]"
# Set log level based on threat score # Set log level based on threat score
http-request set-log-level info if { var(txn.threat_score) -m int lt 20 } http-request set-log-level info if { var(txn.threat_score) -m int lt 20 }