Top Posts Tagged with #aspnetwebapien

IIS 8, HTTP OPTIONS, CORS and ASP.NET Web API

Today I met the challenging problem with one of my web apis running under IIS 8. CORS support which was implemented with nuget library Thinktecture.IdentityModel didn't work properly. Here you can find information how to use this library, and here is the link to configuration issues with IIS. After spending some time with a fiddler tool I found out that the client sends the proper HTTP OPTIONS request, but the response from server lacks Access-Control-Allow-Origin and other useful http headers. After some experiments it turned out that if I enable RAMMFAR option ( runAllManagedModulesForAllRequests="true") in web api web.config, the CORS delegating handler starts to work. However I don't like turning on this option, even if it doesn't really affect all managed modules in IIS, so I kept experimenting. I found out that there is another handler defined in IIS, called OPTIONSVerbHandler. As soon as I removed it via application web.config file, CORS support started to work properly without need to enable RAMMFAR option. This is system.webServer section in web.config:

#en #aspnetwebapi #aspnetwebapien #CORS #IIS

•18+ Adults Only

Watch Anya Live on Cam

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.

✓ Live Streaming✓ Interactive Chat✓ Private Shows✓ HD Quality✓ Free Actions

Free to watch • No registration required • HD streaming

Writing Unit Tests For ASP.NET Web API RC

After I moved one of my solutions to ASP.NET Web API RC I found almost every test broken. A quick investigation shown, that I get null reference exceptions, because of new HttpResponseMessage creation paradigm in ASP.NET Web API RC. Instead of creating new HttpResponseMessage instance, I now have to call Request.CreateResponse() method, and obviously I had null Request in my test environment.

So, I instantiated a new HttpRequestMessage instance and added it to the Request property of the controller being tested. But this was not enough to fix things, and the next problem wasn't that obvious and took time for me to find out the solution.

The next problem was that newly created request message lacked an instajce of HttpConfiguration attached to it. And to attach this configuration to the request message, one have to set this instance into HttpRequestMessage.Properties dictionary by the special key. So, the following is the final code which fixed my tests:

#aspnetwebapi #en #unittest #aspnetwebapien