Hello Railway team,

We need guidance on the officially supported proxy trust configuration for an ASP.NET Core 8 service behind Railway.

Public service URL:

https://joinpia-mobile-api-production.up.railway.app

Our latest verification found:

• Public HTTPS GET /health returns HTTP 200.
• Login through the public HTTPS URL returns HTTP 400: "HTTPS is required."
• An internal login/context test succeeds when X-Forwarded-Proto: https is supplied through a trusted loopback connection.

This suggests that public HTTPS requests reach the application as HTTP and the forwarded protocol is not being accepted under the current trusted proxy configuration.

What is Railway’s officially supported configuration for safely recognizing the original HTTPS scheme in ASP.NET Core?

Please clarify:

1. How the application should identify and trust Railway’s ingress proxies, including any supported stable proxy addresses or ranges.
2. Whether Railway overwrites client-supplied X-Forwarded-Proto and what proxy isolation guarantees apply.
3. The recommended ForwardLimit, or the supported alternative if stable proxy addresses or ranges are unavailable.

We are seeking a supported configuration that preserves HTTPS enforcement, rather than an unofficial broad-trust or trust-all workaround.

Thank you.