dot net Core 3.1 API HttpRequest returns 通常是错误的请求，甚至没有发送请求

Question

我的 HttpRequest 有一个奇怪的问题，我有 2 个应用程序，一个是客户端，另一个是 RESTAPI，问题是我试图通过发送内容为 [=23= 的请求来更新我的实体]

 public async Task<bool> Update(string url, T obj, string id)
    {
        var request = new HttpRequestMessage(HttpMethod.Put, url+id);
        if (obj == null || String.IsNullOrEmpty(id))
        {
            return false;

        }
       
        request.Content = new StringContent(JsonConvert.SerializeObject(obj),
            Encoding.UTF8, "application/json");


        var client = _client.CreateClient();
        client.DefaultRequestHeaders.Authorization =
            new AuthenticationHeaderValue("bearer", GetBearerToken());

        HttpResponseMessage response = await client.SendAsync(request);
        if (response.StatusCode == System.Net.HttpStatusCode.NoContent)
        {
            return true;
        }
        return false;

    }

下面是我的客户端应用程序控制器；

 [HttpPost]
    public async  Task<IActionResult> EditUser([FromForm] UserDTO userDTO ,string id)
    {
        if (!ModelState.IsValid)
        {
            return RedirectToAction("ErrorPage", "Error");
        }
        userDTO.Id = id;
        await _userRepository.Update(EndPoints.UserEndPoint,userDTO,id);
        return RedirectToAction("GetUsers");
    }

而且我不知道是否有必要，因为它甚至没有达到断点，但我还在下面显示了我的 RESTAPI 代码；

 /// <summary>
    /// Update user
    /// </summary>
    /// <param name="id"></param>
    /// <param name="userDTO"></param>
    /// <returns></returns>   
    [HttpPut("{id}")]
    [Authorize(Roles = "Administrator")]
    [ProducesResponseType(StatusCodes.Status200OK)]
    [ProducesResponseType(StatusCodes.Status400BadRequest)]
    [ProducesResponseType(StatusCodes.Status404NotFound)]
    [ProducesResponseType(StatusCodes.Status500InternalServerError)]

    public async Task<IActionResult> UpdateUser(string id, [FromBody] UserDTO userDTO)
    {
        var location = GetControllerActionNames();

        try
        {
            _logger.LogInfo($"{location}: Requested an Update for id: {id} ");

            if (string.IsNullOrEmpty(id) || userDTO == null || id != userDTO.Id)
            {
                _logger.LogError($"{location}: Request for Id: {id} is not sucessful");
                return BadRequest();
            }

            if (!ModelState.IsValid)
            {
                _logger.LogWarn($"{location}: Data was incomplete!");
                return BadRequest(ModelState);
            }

            var isExist = await _userRepo.IsExist(id);
            if (!isExist)
            {
                _logger.LogWarn($"{location}: with Id: {id} is not exisist");
                return NotFound();
            }

            



            var usermap = _mapper.Map<CompanyUser>(userDTO);



            if (usermap == null)
            {
                _logger.LogWarn($"{location}:  Data is empty");
                return BadRequest();
            }

            var response = await _userRepo.Update(usermap);

            if (!response)
            {
                _logger.LogError($"{location}: Update is failed ");
                return NotFound();
            }
            _logger.LogInfo($"User is Updated");
            return NoContent();
        }
        catch (Exception e)
        {

            return InternalError($"{location} - {e.Message} - {e.InnerException}");
        }
    }

当我尝试使用 PostMan 时，RESTAPI 代码正在运行。但是从我发送请求的客户端来看，它有时会工作，但通常会立即给出错误的请求作为响应，我的意思是甚至不去我的 RESTAPI。你能帮忙解决这个奇怪的问题吗

Answer 1

我在 API 登录时解决了这个问题因为我正在使用 Microsoft Identity 并且当我使用 await PasswordEmailSignInAsync(userName, password, false, false); 时它会自动在我的 API 端生成应用程序 cookie，并且我使用 fiddler 来捕获请求并且当我收到错误或在我的API 当线程退出时，应用程序 cookie 也会在此之后过期，当我从我的客户端向我的 API 发出新请求时，它立即在我的客户端发出了错误的请求。

所以我将登录方法更改为var user = await _userManager.FindByEmailAsync(userDTO.Email); var result = await _userManager.CheckPasswordAsync(user, userDTO.Password);

为了避免从应用程序创建cookie。我的应用程序中已经有 JWT 令牌结构，但没有用，因为默认的 authorized 属性没有使用 bearer schema，我修改了我的 startup.cs [ ]授权属性不与 ASP.Net Core1

中的 JWT 访问令牌一起使用

现在一切正常！

[Route("login")]
    [HttpPost]
    [AllowAnonymous]
    [ProducesResponseType(StatusCodes.Status200OK)]
    [ProducesResponseType(StatusCodes.Status401Unauthorized)]
    public async Task<IActionResult> Login([FromBody] UserLoginDTO userDTO)
    {

        var location = GetControllerActionNames();
        try
        {
            var userName = userDTO.Email;
            var password = userDTO.Password;
         
            _logger.LogInfo($"{location}: User:{userName} - Attempted to Login");
            //var result = await PasswordEmailSignInAsync(userName, password, false, false);
            var user = await _userManager.FindByEmailAsync(userDTO.Email);
            var result = await _userManager.CheckPasswordAsync(user, userDTO.Password);

           
            if (result)
            {
              
                _logger.LogInfo($"{location}: User:{userName} Logged in Succesfully");
                var tokenstring = await GenerateJSONWebToken(user);
                return Ok(new { token = tokenstring });
            }
            _logger.LogWarn($"{location}: User:{userName} couldnt logged in ");
            return Unauthorized(userDTO);
        }
        catch (Exception e)
        {

            return InternalError($"{location} - {e.Message} - {e.InnerException}");
        }
    }

dot net Core 3.1 API HttpRequest returns 通常是错误的请求，甚至没有发送请求

dot net Core 3.1 API HttpRequest returns usually bad request without even sending the request

json

asp.net-core-mvc

httprequest

httpresponse

bad-request