Advantages of HttpContext Forwarding

When integrating with third-party API endpoints, the common approach is to create an entry program and call the HTTP remote request service within it to send requests to the specified third-party endpoint. Assume the third-party endpoint's controller is defined as follows:

12345678910

[ApiController][Route("[controller]/[action]")]public class VendorController : ControllerBase{    [HttpPost]    public VendorModel Add(VendorModel model)    {        return model;    }}

The traditional approach is to use the HTTP remote request service to send the request, for example:

12345678910111213

[ApiController][Route("[controller]/[action]")]public class YourController(IHttpRemoteService httpRemoteService) : ControllerBase{    [HttpPost]    public async Task<VendorModel> AddVendorAsync()    {        return await httpRemoteService.SendAsync<VendorModel>(            HttpRequestBuilder.Post("https://www.furion.net/vendor/add")                .SetJsonContent(new VendorModel())        );    }}

However, by using the HttpContext forwarding feature, we can simplify the code. We only need to create a controller declaration that matches the third-party endpoint's interface, such as the Add method of VendorController, as shown below:

123456789101112

[ApiController][Route("[controller]/[action]")]public class YourController(IHttpContextAccessor httpContextAccessor) : ControllerBase{    [HttpPost]    public async Task<VendorModel> AddAsync(VendorModel model)  // Both synchronous and asynchronous are supported    {        // Automatically forwards the model, no additional setup required        return await httpContextAccessor.Context            .ForwardAsync<VendorModel>("https://www.furion.net/vendor/add");    }}

In this way, the code becomes more concise and clear. Instead of manually building and sending the HTTP request, we leverage the HttpContext forwarding feature to directly invoke the third-party endpoint.

Leveraging the X-Forward-To Request Header to Improve Code Flexibility

In addition to explicitly setting the target address in code, we can also automatically obtain the forwarding address through the client request's X-Forward-To header. Assuming the client has already set the request header X-Forward-To: https://www.furion.net/vendor/add, our code can be further simplified as follows:

1234567891011

[ApiController][Route("[controller]/[action]")]public class YourController(IHttpContextAccessor httpContextAccessor) : ControllerBase{    [HttpPost]    public async Task<VendorModel> AddAsync(VendorModel model)  // Both synchronous and asynchronous are supported    {        // Automatically resolves the X-Forward-To header address from the request        return await httpContextAccessor.Context.ForwardAsync<VendorModel>();    }}

In this way, the code becomes even more concise and flexible, and is able to dynamically forward any content to the target address. This approach has enormous potential, and you can explore and experiment with it according to your needs.