[英]How to handle multiple endpoints in ASP.Net Core 3 Web API properly
I have 2 methods to handle HTTP GET requests, first one for int
type input and the other one for string
type input.我有两种方法来处理 HTTP GET 请求,第一种用于
int
类型输入,另一种用于string
类型输入。
//GET : api/Fighters/5
[HttpGet("{id}")]
public async Task<ActionResult<Fighter>> GetFighter(int id)
{
var fighter = await _context.Fighters.FindAsync(id);
if (fighter == null)
{
return NotFound();
}
return fighter;
}
// GET: api/Fighters/Alex
[Route("api/Fighters/{name}")]
[HttpGet("{name}")]
public async Task<ActionResult<IEnumerable<Fighter>>> GetFighter (string name)
{
return await _context.Fighters.Where(f => f.Name == name).ToListAsync();
}
when i send HTTP GET this exception appears (in Postman):当我发送 HTTP GET 时出现此异常(在邮递员中):
Microsoft.AspNetCore.Routing.Matching.AmbiguousMatchException: The request matched multiple endpoints. Matches:
FighterGameService.Controllers.FightersController.GetFighter (FighterGameService)
FighterGameService.Controllers.FightersController.GetFighter (FighterGameService)
FighterGameService.Controllers.FightersController.GetFighter (FighterGameService)
FighterGameService.Controllers.FightersController.GetFighter (FighterGameService)
at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.ReportAmbiguity(CandidateState[] candidateState)
at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.ProcessFinalCandidates(HttpContext httpContext, CandidateState[] candidateState)
at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.Select(HttpContext httpContext, CandidateState[] candidateState)
at Microsoft.AspNetCore.Routing.Matching.DfaMatcher.MatchAsync(HttpContext httpContext)
at Microsoft.AspNetCore.Routing.Matching.DataSourceDependentMatcher.MatchAsync(HttpContext httpContext)
at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
GET api/fighters/1
would cause error obviously since " 1
" could be either int
or string
so i solved my problem by combining two methods: GET api/fighters/1
显然会导致错误,因为“ 1
”可能是int
或string
所以我通过结合两种方法解决了我的问题:
// GET: api/Fighters/5
// GET: api/Fighters/Alex
[HttpGet("{idOrName}")]
public async Task<ActionResult<IEnumerable<Fighter>>> GetFighter(string idOrName)
{
if (Int32.TryParse(idOrName, out int id))
{
return await _context.Fighters.Where(f => f.Id == id).ToListAsync();
}
else
{
return await _context.Fighters.Where(f => f.Name == idOrName).ToListAsync();
}
}
this works however this doesn't feel right at all.这行得通,但这根本感觉不对。 What is the proper way to handle this problem?
处理这个问题的正确方法是什么?
You can use route constraint您可以使用路线约束
[HttpGet("{id:int}")]
public async Task<ActionResult<Fighter>> GetFighter(int id)
[HttpGet("{name}")]
public async Task<ActionResult<IEnumerable<Fighter>>> GetFighter (string name)
I had this problem in Core 3.0.我在 Core 3.0 中遇到了这个问题。 I finally found the solution was to put a route attribute on the action - eg
[Route("NodeInfo")]
.我终于发现解决方案是在动作上放置一个路由属性 - 例如
[Route("NodeInfo")]
。 That fixed it那解决了它
Please follow the solution for.Net Core 3.1 or higher Version:Use [Route("RouteName")]请按照.Net Core 3.1或更高版本的解决方案:使用[Route("RouteName")]
[HttpPost]
[Route("CreateUserRole")]
// [Authorize(Roles = "admin")]
[ProducesResponseType(StatusCodes.Status201Created)]
[ProducesResponseType(StatusCodes.Status400BadRequest)]
[ProducesResponseType(StatusCodes.Status500InternalServerError)]
public async Task<IActionResult> CreateUserRole([FromBody] AssignUserRole assignUserRole)
{
try
{
_logger.LogInfo("Attempted submission attempted");
if (assignUserRole == null)
{
_logger.LogWarn("Empty request submitted");
return BadRequest(ModelState);
}
if (!ModelState.IsValid)
{
_logger.LogWarn("User data was incomplete");
return BadRequest(ModelState);
}
var User = _Mapper.Map<Users>(assignUserRole);
_UserRoleRepository.AssignRoleUser(assignUserRole);
_logger.LogInfo("User Role created");
Audit_logs audit = new Audit_logs()
{
uid = User.id,
action = "Create User Role",
log = $"{assignUserRole.rolename} Role has created",
datetime = DateTime.Now
};
await _audit_Logs.Create(audit);
return Created("Create User Role", new { assignUserRole });
}
catch (Exception ex)
{
return InternalError($"{ex.Message}-{ex.InnerException}");
}
}
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.