Issue Description: Since March 25, 2026, real client IP addresses are completely missing when accessing my service through Railway's Fastly CDN. All IP-related headers only contain the Fastly edge IP instead of the real client IP.

Service Details:

• Project: featheryun_album
• Environment: production
• Service ID: 3c2793b3-f7d0-4238-9443-628b45d743c5

Timeline:

• March 24: Working correctly, real client IP was present
• March 25: Issue started, IP headers missing
• Now (March 26): Issue still persists

Actual Request Headers Output:

Remote Address (client.host): 157.52.95.46
X-Forwarded-For: 157.52.95.46
True-Client-IP: N/A (not present)
CF-Connecting-IP: N/A (not present)
X-Real-IP: 157.52.95.46
cdn-loop: Fastly;wasm=yKdHIfODh6d0uwGZ94vIRLBHkhqgeQMo2eWEb5r7iw1ahT1dyMGNTXxZVkQxlwJpdgN3P7EXsVljeRFKZxnlEXYXoceN0lvLrp19uAA

Key Findings:

• All three IP-related headers (X-Forwarded-For, X-Real-IP, client.host) only contain the Fastly edge IP 157.52.95.46
• Real client IP is completely missing
• The wasm= parameter in the cdn-loop header indicates traffic is passing through a WASM edge
• This appears to correlate with a Railway Fastly WASM edge configuration change on March 25

Expected Behavior:

• X-Forwarded-For should contain the real client IP (possibly along with Fastly edge IP)
• True-Client-IP should contain the real client IP
• At least one header should contain the real client IP, not just the Fastly edge IP

Impact: Unable to correctly log visitor IPs, affecting logging, analytics, and security features.