This release focuses on hardening request handling against a specific header-spoofing pattern that could force unnecessary server errors.
Security and stability fix
Requests with a caller-supplied Client-IP header no longer cause unhandled IpSpoofAttackError failures. Previously, a mismatched Client-IP versus X-Forwarded-For could trigger a plain 500 response before normal error handling and request protections had a chance to run.
Now, the app drops the untrusted Client-IP header early, so request.remote_ip continues to come from X-Forwarded-For. This prevents unauthenticated callers from generating avoidable 500s and keeps these requests flowing through the usual safeguards.