All checks were successful
HAProxy Manager Build and Push / Build-and-Push (push) Successful in 1m54s
- Removed all 40X error tracking and rate limiting from HAProxy templates - Preserved critical IP forwarding headers (X-CLIENT-IP, X-Real-IP, X-Forwarded-For) - Kept stick table and IP blocking infrastructure for potential future use - Rate limiting can now be implemented at container level with proper context This change prevents legitimate developers from being rate-limited during normal development activities while maintaining proper client IP forwarding for container-level security and logging. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
15 lines
661 B
Smarty
15 lines
661 B
Smarty
|
|
backend {{ name }}-backend
|
|
option forwardfor
|
|
# Pass the real client IP to backend (from proxy headers or direct connection)
|
|
# This is crucial for container-level logging and security tools
|
|
http-request add-header X-CLIENT-IP %[var(txn.real_ip)]
|
|
http-request set-header X-Real-IP %[var(txn.real_ip)]
|
|
http-request set-header X-Forwarded-For %[var(txn.real_ip)]
|
|
{% if ssl_enabled %}http-request set-header X-Forwarded-Proto https if { ssl_fc }{% endif %}
|
|
|
|
|
|
{% for server in servers %}
|
|
server {{ server.server_name }} {{ server.server_address }}:{{ server.server_port }} {{ server.server_options }}
|
|
{% endfor %}
|
|
|