⚡ 𝟭𝟮 𝗥𝘂𝗹𝗲𝘀 𝗳𝗼𝗿 𝗠𝗶𝗱𝗱𝗹𝗲𝘄𝗮𝗿𝗲 𝗢𝗿𝗱𝗲𝗿𝗶𝗻𝗴 𝗶𝗻 𝗔𝗦𝗣.𝗡𝗘𝗧 𝗖𝗼𝗿𝗲

These rules ensure your API is secure, performant, and predictable.

Break them, and you’ll debug for hours.

- Use UseForwardedHeaders() first if behind a proxy
- Force redirect to HTTPS early with UseHttpsRedirection()
- Call UseRouting() before any middleware that depends on route data
- Apply UseCors() after routing but before authentication
- Add UseAuthentication() before authorization
- Always place UseAuthorization() after routing to enforce policies
- Put UseExceptionHandler() near the top to catch all errors early
- Set UseRateLimiter() early to shield your API from overload
- Call UseResponseCompression() after routing and before endpoints
- Register UseStaticFiles() before routing only if serving static content
- Place custom middleware (logging, tracing) early to cover the full request
- UseEndpoints() must be last to execute matched endpoints and terminate the pipeline.