Inject dependency into DelegatingHandler

Question

I am new to dependency injection, but happy with Ninject and Ninject.Extensions.Logging to [Inject] my ILogger wherever i need it.

However some DelegatingHandlers are spoiling all the fun.

public class HttpsHandler : DelegatingHandler
{
    [Inject]
    public ILogger Logger { get; set; }

    protected override Task<HttpResponseMessage> SendAsync(
            HttpRequestMessage request, CancellationToken cancellationToken)
        {
            if (!string.Equals(request.RequestUri.Scheme, "https", StringComparison.OrdinalIgnoreCase))
            {
                Logger.Info(String.Format("{0}: is using HTTP", request.RemoteAddress());
                return
                    Task.Factory.StartNew(
                        () =>
                        new HttpResponseMessage(HttpStatusCode.BadRequest)
                        {
                            Content = new StringContent("HTTPS Required")
                        });
            }

            return base.SendAsync(request, cancellationToken);
        }
 }

Could anyone point me in the right direction on how to Inject Ninject.Extensions.Logger.Nlog2 into Ilogger inside the delegatinghandlers?

Update

I think Pete got me in the right direction in the comments (thanks!). I added the following constructor to the HttpsHandler:

public HttpsHandler()
        {
            var kernel = new StandardKernel();

            var logfactory = kernel.Get<ILoggerFactory>();
            this.Logger = logfactory.GetCurrentClassLogger();
        }

and now i've got the Logger working!

My only question left, is this the right way to do it, or is it a anti-pattern?

What's creating HttpsHandler instances? If it's not being created by NInject, then that's going to be a problem. — Pete, Feb 07 '13 at 16:55
@Pete Thanks for your answer, I think you got me in the right direction, could you maybe have a look at my updated question? — Jos Vinke, Feb 07 '13 at 17:19
If you "Inject [your] ILogger wherever [you] need it", please take a look at [this stackoverflow q/a](http://stackoverflow.com/questions/9892137/windsor-pulling-transient-objects-from-the-container). — Steven, Feb 08 '13 at 09:28
@Steven thanks for the interesting read. It's some nice thinking food and I'll certainly make use off it, now I just need to figure out the best way to do so. — Jos Vinke, Feb 08 '13 at 10:06
@JosVinke: It can be hard to implement these patterns in an existing (or legacy) code base, but in my experience, it usually pays off (but always do it one step at the time). Good luck. — Steven, Feb 08 '13 at 10:18

Filip W · Accepted Answer · 2013-02-07T22:38:05.423

26

DelegatingHandlers are only initialized once in Web API, at application start.

This is a known issue/design feature of Web API (I presume for performance reasons) - see the bug report here http://aspnetwebstack.codeplex.com/workitem/62.

Using a constructor initialization like you suggested yourself, would only work if you have singleton-type dependencies (that' why you logger works). Regardless, if you want to delegate the resolution to Web API DependencyResolver you have to use GetDependencyScope(), which can be called off the HttpRequestMessage, as a workaround.

I posted a walkthrough on doing that with Ninject a while ago. You should use this approach to resolve your deendency, because with your current solution you have coupled Ninject & your handler, which is far from desired.

edited Feb 07 '13 at 22:38

answered Feb 07 '13 at 22:32

Filip W

27,097
6
95
82

Thanks I think i've got your solution working (nice blog!), I just can't verify because I get a null reference when the dependency is resolved in the GetService method. ( at Ninject.Extensions.Logging.LoggerFactoryBase.GetLogger(IContext context) in c:\Projects\Ninject\ninject.extensions.logging\src\Ninject.Extensions.Logging\LoggerFactoryBase.cs:line 61). Could you confirm this is a bug in Ninject.Extensions.Logging or did I do something wrong? – Jos Vinke Feb 08 '13 at 12:52
Well *GetService* is simply resolving from *kernel.Get*. SO you need to register the logger at application startup - something like *kernel.Bind().To()*. I am not familiar with ninject.extensions.logging so not sure how *exactly* you do that, but it has to be defined at application startup, where you register all dependencies. *GetDependencyScope()* is simply a shortcut to resolve something from your Ninject kernel, without explicitly specifying it (without coupling yourself to the Ninject kernel, since you can easily change DI provider and this code will still work). – Filip W Feb 08 '13 at 13:25
The service is registered and it also gets to the LoggerFactory (see the trace) also if i register it (again) i get a exception that multiple ILoggers are registered. For now I'll mark your answer as accepted and i'll give it a shot with another dependency when i've got a little more time on my hands. Thanks for the help. – Jos Vinke Feb 08 '13 at 13:29
I just wanted to let you know that I had another scenario where this came really handy and that your solution worked great, thanks! – Jos Vinke Feb 11 '13 at 16:31

score 4 · Answer 2 · answered Oct 18 '16 at 08:46

4

I am using this:

 protected override async Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
 {
    var service = GlobalConfiguration.Configuration.DependencyResolver.GetService(typeof(IFooService)) as IFooService;
    // Other stuff
 }

answered Oct 18 '16 at 08:46

Barbaros Alp

6,405
8
47
61

I was trying to use this from within my own NuGet package that didn't know about GlobalConfiguration. I was able to find it in the [Microsoft.AspNet.WebApi.WebHost](https://www.nuget.org/packages/Microsoft.AspNet.WebApi.WebHost/) package. – Ecyrb Feb 24 '19 at 23:28

score 1 · Answer 3 · edited Oct 20 '14 at 17:17

1

I think what you need is this.

It's the Ninject dependency resolver for MVC. Then I believe you need to use:

GlobalConfiguration.Configuration.ServiceResolver.SetResolver()

And pass in the NInject dependency resolver.

edited Oct 20 '14 at 17:17

abatishchev

98,240
88
296
433

answered Feb 07 '13 at 17:25

Pete

6,585
5
43
69

I have tried your solution, but I can't really figure it out. I'm using Asp.Net WebApi (updated tags) and ServiceResolver doesn't exist, it is DependencyResolver in Web Api. I tried a custom DependencyResolver but without any luck. Any other suggestions? Thanks anyway +1 for the help so far. – Jos Vinke Feb 07 '13 at 18:38
Ah, don't really know, then. Your initial tag said asp.net MVC, so that was the solution I knew. Sorry. maybe someone else can help you. – Pete Feb 07 '13 at 21:21
Yeah I tagged it with MVC because it's a MVC delegatinghandler and not a HTTP delegatinghandler. Like HTTP Controllers vs MVC Controllers which are both used in a Web Api application. Confuse them and you're up for a fun time solving things. That's why I tagged MVC but sorry for the inconvenience and thanks for the time spend :) – Jos Vinke Feb 07 '13 at 22:24

score 0 · Answer 4 · answered Jul 19 '15 at 14:36

I had a similar situation and taking hints from this post and related links, I came up with following constructor injection solution that seems to work ok for me:

using Ninject.Extensions.Logging;

public static void Register(HttpConfiguration config) {

ILoggerFactory loggerFactory =
   config.DependencyResolver.GetService(typeof(ILoggerFactory))
   as ILoggerFactory;
config.MessageHandlers.Add(
   new HttpsHandler(loggerFactory.GetLogger(typeof(HttpsHandler))));

// Other codes ...

}

I am though using Ninject for WebAi 2/log4net and have installed all pertinent nuget packages

Inject dependency into DelegatingHandler

4 Answers4

Linked