.NET多环境通用URL配置咨询：支付重定向URL适配生产环境方案

1. 多环境配置分离 #

把不同环境的URL拆分到对应环境的配置文件中，彻底避免硬编码：

• 开发环境配置文件appsettings.Development.json：

"PaymentCallBack": {
  "ReturnUrl": "https://localhost:7089/api/Payment/callback-payment",
  "FrontendSuccessUrl": "http://localhost:5173/success"
}

• 生产环境配置文件appsettings.Production.json：

"PaymentCallBack": {
  "ReturnUrl": "https://your-production-domain.com/api/Payment/callback-payment",
  "FrontendSuccessUrl": "https://your-production-frontend.com/success"
}

2. 绑定配置类并注入 #

创建配置实体类映射配置节点：

public class PaymentSettings
{
    public string ReturnUrl { get; set; }
    public string FrontendSuccessUrl { get; set; }
}

在Program.cs中注册配置服务：

builder.Services.Configure<PaymentSettings>(builder.Configuration.GetSection("PaymentCallBack"));

3. 修改回调方法代码 #

在控制器中通过IOptions<PaymentSettings>注入配置，替换硬编码的URL：

private readonly IOptions<PaymentSettings> _paymentSettings;
private readonly ILogger<PaymentController> _logger;
private readonly IPaymentService _paymentService;

public PaymentController(IOptions<PaymentSettings> paymentSettings, ILogger<PaymentController> logger, IPaymentService paymentService)
{
    _paymentSettings = paymentSettings;
    _logger = logger;
    _paymentService = paymentService;
}

public async Task<IActionResult> PaymentCallback()
{
    _logger.LogInformation("Start save bill");
    var response = await _paymentService.PaymentExecute(Request.Query);

    return Redirect(_paymentSettings.Value.FrontendSuccessUrl);
}

4. 动态生成回调地址（可选） #

如果回调地址需要适配不同部署域名，可以通过请求上下文动态生成：

// 自动获取当前站点的协议+域名，拼接回调路径
var dynamicCallbackUrl = $"{Request.Scheme}://{Request.Host}/api/Payment/callback-payment";

方案说明 #

.NET官方配置系统原生支持多环境适配，核心是通过ASPNETCORE_ENVIRONMENT环境变量指定运行环境，自动加载对应环境的配置文件，结合IOptions模式实现配置的解耦注入，这就是实现多环境通用URL的标准方案。

内容的提问来源于stack exchange，提问作者user16778385