self-hosting

I have a console application SERVER that hosts WebApi controllers using OWIN self-hosting, and runs under a custom account named "ServiceTest1". In the same machine I have another console application CLIENT that runs under the account "ServiceTest2", and I want to capture in SERVER that "ServiceTest2" invoked a controller action. However: WindowsIdentity.GetCurrent() is always "ServiceTest1". Thread.CurrentPrincipal is an unauthenticated GenericIdentity . RequestContext.Principal is null. User is null. What do I need to make this WebApi OWIN self-hosted to grab the Windows identity of the

WCF 4.5 supports GZIP without third party libraries or handwritten extensions. I got it working via TCP Binding, but cannot find a way to get it working via HTTP Binding. my wcf - Service is self hosted in a windows service. Addon: i am not allowed to use IIS; i can't switch to any WCF replacement. this works with gzip: binding="customBinding" bindingConfiguration="tcpCompressionBinding" name="tcp" and this is what i currently use for http: binding="basicHttpBinding" bindingConfiguration="httpBinding" name="http" The documentation does not really help me: http://msdn.microsoft.com/en-us

In the ASP.NET Web API , HttpControllerContext instances provide a lot of information about the current environment, including the URI of the current request. If a service relies on such information (e.g. the request URI), it should be possible to inject that information into the service. This is pretty easy to do using Poor Man's DI: just implement a custom IHttpControllerActivator . However, with Castle Windsor this suddenly becomes very difficult. Previously, I've described a very convoluted way to resolve this issue, but it hinges on the PerWebRequest lifestyle, and it turns out that this

I'm working on a self-hosted ASP.NET web api-application. Everything works fine, but now I'm struggling with HttpContext : I need to save session-informations from the client. But HttpContext.Current is always null. So it's obvious that my HttpSelfHostServer don't work with the static HttpContext-Class. The thing I don't understand is: why..? And I can't figure out a way to tell neither HtttpSelfHostServer nor HttpSelfHostConfiguration to work with HttpContext . Here's what I'm doing: Creating a HttpSelfHostConfiguration 1.1 Adding Service-Resolvers & Routes 1.2 Adding custom UserNamePassword