Скачать или смотреть Can an ASP.NET Core Web API Controller Have More Than One ControllerRoute?

Discover how to effectively manage `POST` requests in ASP.NET Core Web API Controllers, ensuring parameters are correctly handled even with multiple `ControllerRoute` setups.
---
This video is based on the question https://stackoverflow.com/q/68759223/ asked by the user 'Qiuzman' ( https://stackoverflow.com/u/5021945/ ) and on the answer https://stackoverflow.com/a/68776298/ provided by the user 'Serge' ( https://stackoverflow.com/u/11392290/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Can an ASP.NET Core Web API Controller have more than one ControllerRoute?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding ASP.NET Core Web API Controller Routing

When working with ASP.NET Core Web API Controllers, one common question arises: Can a controller have more than one ControllerRoute? This query typically emerges when developers are faced with challenges in handling different HTTP requests, particularly POST requests, resulting in issues with parameter binding. In this guide, we will explore the problem, discuss the common pitfalls, and provide solutions to ensure your API endpoints function seamlessly.

The Problem

A developer recently faced a situation where their GET requests were processing correctly while the POST requests failed to receive parameter values. Here are the key observations:

GET Request Worked: The parameters passed into the Contacts action were being correctly captured.

POST Request Failed: The AddFirm action could not retrieve parameters from the POST request, despite their presence in the frontend JavaScript payload.

The Existing Setup

The existing routing configuration for the API requests was set as follows:

[[See Video to Reveal this Text or Code Snippet]]

This setup functioned well for GET requests but omitted the appropriate handling required for POST.

Solutions to Enhance POST Request Handling

To ensure that your ASP.NET Core Controller can effectively handle POST requests, especially when using the [FromBody] attribute, follow these structured solutions:

1. Stringify the Data

When utilizing the [FromBody] attribute in your action method, it is essential to send data in JSON format. Here's how you can modify your JavaScript code:

[[See Video to Reveal this Text or Code Snippet]]

2. Use a ViewModel for Multiple Properties

If your POST action requires multiple parameters, it's best practice to consolidate these into a single object. You can achieve this by creating a ViewModel class:

[[See Video to Reveal this Text or Code Snippet]]

Then, update your action method to accept this ViewModel:

[[See Video to Reveal this Text or Code Snippet]]

3. Update the AJAX Request

Make sure your AJAX request sends the data in the format expected by your action method. Here’s how to structure the AJAX call with multiple properties:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By taking these steps, you can ensure that your ASP.NET Core Web API Controller effectively handles both GET and POST requests, eliminating the issues of parameter binding. The key takeaway is the importance of sending data in the expected format and efficiently structuring your actions to accept multiple parameters when needed.

If you find yourself implementing multiple controller routes, remember to keep your request configurations and payload structures consistent for optimal API performance. Happy coding!