HttpClient.PostAsync() send Get requests

[olkuziv]

Describe the bug

After adding [Authorize] attribute on Post method, aftert calling HttpClient.PostAsync() working like GetAsync().

To Reproduce

Steps to reproduce the behavior:

1. Create default blazor app
2. Add Coockies auth
3. Add new Get endpoint
4. Add [Authorize] attribute for new Post endpoint
5. Call this Post endpoint
6. In debug could see that HttpClient send Get request

Screenshots

[olkuziv]

After adding handler

PostAsync returns "Found 302" status code, but endpoid still not working.

[dcarr42]

There is certainly some weirdness here. What are you expecting to be returned from the endpoint?

Regards to the response with the auth challenge, that's normal.
You may need to reconsider how you initiate the auth flow with respect to the blazor client. There will be developments in this area so you may need to consider future best practices.

#4048

[enetstudio]

@olkuziv, HttpClient is automatically added to your application as a Singleton service. The HttpClient is based on the WebAssemblyHttpMessageHandler. Why do you add HttpClient as a scoped service, and based on HttpClientHandler ? I'm not suggesting that it is related to your issue...just wondering why you coded that way ?

[enetstudio]

@olkuziv, perhaps this link can solve your problem:
https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclienthandler?view=netcore-3.0#httpclienthandler-in-net-core

[mkArtakMSFT]

Thanks for contacting us, @olkuziv.
You're most probably being auto-redirected by the server to the authentication endpoint, which is the expected behavior when using the CookieAuthentication. So your HttpClient automatically sends a get request to the authentication endpoint, and that's what you're observing here. To successfully make the request, make sure that the user is authenticated and you pass the cookie as part of the first request.

[olkuziv]

Thanks for contacting us, @olkuziv.
You're most probably being auto-redirected by the server to the authentication endpoint, which is the expected behavior when using the CookieAuthentication. So your HttpClient automatically sends a get request to the authentication endpoint, and that's what you're observing here. To successfully make the request, make sure that the user is authenticated and you pass the cookie as part of the first request.

Yes, You are right. I should pass cookies in HttpClient headers