cap5lut
✅ Sending an HTTP GET request with a JSON body and then reading it in the .NET Core Web Server
that 404 might be a hint that u were still running an old version, where that endpoint simply didnt exist yet.
because it doesnt make sense to respond with that status code
84 replies
✅ Sending an HTTP GET request with a JSON body and then reading it in the .NET Core Web Server
http://localhost:53415/Api/User/new was the old URI
so the endpoint is /Api/User/new and the old base address was localhost:53415 for HTTP
from the logs u showed earlier, u can see that the new base addresses are localhost:5001 for HTTPS and localhost:5000 for HTTP
so the new URI for that endpoint should be: http://localhost:5000/Api/User/new84 replies
✅ Sending an HTTP GET request with a JSON body and then reading it in the .NET Core Web Server
the weird thing is actually that u get a 404 after all,
from various online resources (cant test it right now locally), it should be either a 400 response code (bad request),
or ur model binding simply wouldnt work
84 replies
✅ Sending an HTTP GET request with a JSON body and then reading it in the .NET Core Web Server
you probably will have to set up HTTP logging
84 replies
✅ Sending an HTTP GET request with a JSON body and then reading it in the .NET Core Web Server
i assume u r using visual studio and i cant check there how to start it that way, because i am using jetbrains rider.
but essentially u could open the terminal, go to the project folder and execute
dotnet run and it should start as standalone process without iis express84 replies