asp.net-core-webapi

I solved this problem after not finding the solution on Stackoverflow, so I am sharing my problem here and the solution in an answer. After enabling a cross domain policy in my .NET Core Web Api application with AddCors, it still does not work from browsers. This is because browsers, including Chrome and Firefox, will first send an OPTIONS request and my application just responds with 204 No Content. Niels Brinch Add a middleware class to your project to handle the OPTIONS verb. using System.Threading.Tasks; using Microsoft.AspNetCore.Builder; using Microsoft.AspNetCore.Http; using Microsoft

I'm developing an ASP.Net Core web application where I need to create a kind of "authentication proxy" to another (external) web service. What I mean by authentication proxy is that I will receive requests through a specific path of my web app and will have to check the headers of those requests for an authentication token that I'll have issued earlier, and then redirect all the requests with the same request string / content to an external web API which my app will authenticate with through HTTP Basic auth. Here's the whole process in pseudo-code Client requests a token by making a POST to a

I want the example controller below to return a status code 418 with no contents. Setting the status code is easy enough but then it seems like there is something that needs to be done to signal the end of the request. In MVC prior to ASP.NET Core or in WebForms that might be a call to Response.End() but how does it work in ASP.NET Core where Response.End does not exist? public class ExampleController : Controller { [HttpGet][Route("/example/main")] public IActionResult Main() { this.HttpContext.Response.StatusCode = 418; // I'm a teapot // How to end the request? // I don't actually want to

I have an ASP.NET MVC site, IdentityServer4 host and a web API. When I log in the MVC site, using external provider (Facebook), I'm logged in fine. From the MVC site I can also consume the web API correctly. However, the next day, I'm still logged in into the MVC site, but when I then try to access the web API, I get a 'not authorized exception'. So although I'm still logged in in the MVC site, I'm not authenticated anymore to call a web API from within the MVC site. I'm wondering how to handle this situation, and how IdentityServer4 should be configured. Why am I still logged in the MVC site

I'm trying to make a simple API call from a .NET Core MVC application: using (var client = new HttpClient()) { client.BaseAddress = new Uri("http://localhost:49897"); var response = client.GetAsync("some-route").Result; var dataString = response.Content.ReadAsStringAsync().Result; // Unexpected data here. See below. [...] // deserialize dataString } client.GetAsync(route) successfully hits an API action method, which ultimately does this: public HttpResponseMessage Get([FromUri] BindingModel bindingModel) { List<SomeModel> resultObjects; [...] // populate resultObjects with data return Request