如何为指定HttpGet方法正确创建CreatedAtRoute？换用CreatedAtAction是否合规？

Absolutely, using CreatedAtAction here is a totally compliant and often more straightforward solution for your scenario! Let me break this down for you:

Why Your Original CreatedAtRoute Failed #

Your GetExchangePoint action is decorated with [HttpGet("exchangepoint")], but you didn't explicitly assign a route name to it (via [Route(Name = "GetExchangePoint")]). The CreatedAtRoute method relies on matching a named route to generate the URL, so when you passed "GetExchangePoint" as the route name parameter, the routing system couldn't find a route with that name, leading to failure.

Why CreatedAtAction Works (and Is Compliant) #

CreatedAtAction is designed to generate URLs by targeting an action directly (by name, plus controller if needed) rather than relying on named routes. In your working code:

• You specify the action name ("GetExchangePoint"), controller name ("ShippingPlaceData"), and the required name parameter
• The framework correctly resolves the route to your existing action and generates the proper URL for the newly created ExchangePointDto

This aligns perfectly with HTTP standards for a 201 Created response: you're returning the correct status code, including a URL to the newly created resource in the Location header, and sending the resource body itself. This is a fully REST-compliant approach.

When to Choose CreatedAtRoute vs CreatedAtAction #

• Use CreatedAtRoute if you've defined explicit named routes (e.g., [Route("exchangepoint", Name = "GetExchangePoint")]). Named routes are useful if you want to decouple URL generation from action/controller names (in case you rename them later without breaking URLs).
• Use CreatedAtAction when you don't have named routes, or when you want a simpler, more direct way to target an action in the same or another controller. It's the more intuitive choice for most basic scenarios like yours.

In short, your switch to CreatedAtAction is not just a workaround—it's a perfectly valid, recommended implementation that meets all relevant HTTP and REST conventions.

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