developer-delphi-horse-clientip

To get the real client IP in Delphi Horse behind a reverse proxy, call ClientIP(Req) within a THorse route. It prioritizes proxy headers like CF-Connecting-IP and X-Forwarded-For, falling back to the direct TCP IP if unavailable.

Proxy headers prioritized for client IP extraction in Horse requests include CF-Connecting-IP, X-Real-IP, and X-Forwarded-For. The Skill checks these in order and applies fallbacks to the direct socket IP to ensure reliable detection behind proxies.

Your Delphi Horse app logs the proxy IP instead of the real client IP because direct socket connections behind load balancers mask the origin. You need to parse proxy headers like X-Forwarded-For with proper header ordering and error handling to capture the actual client IP.

Yes, you can use this client IP extraction for rate limiting and security logging in Horse. It consistently captures the client's origin IP from proxy headers, satisfying IT compliance requirements and enabling accurate audit trails for requests behind load balancers.

Extracting the client IP in Horse requires no specific external dependencies or components. It integrates directly with THorse middleware to apply header order, fallbacks, and error handling natively within your Delphi Horse application.