6

Is there a practical way to access the attributes decorating a controller or action from a Message Handler/ DelegatingHandler?

From the diagram on Pedro Felix's blog entry, it looks like Message Handler's are too early in the pipeline and the info won't be available until the Controller Dispatcher Message Handler runs. Correct?

About my use case:
I'm working with the Thinktecture identity model, and it would be useful to be able to look for the AllowAnonymous attribute in the AuthenticationHandler.

EBarr
  • 11,826
  • 7
  • 63
  • 85

1 Answers1

2

By nature, this seems to be the wrong place to implement it. As you have noted, Message Handlers work across all requests and responses. If you depend on an attribute, this would naturally be a filter. So I suggest you follow that route.

In fact in the handler you cannot assume there is going to an ApiController or an action. Handlers can be equally used on clients.

Aliostad
  • 80,612
  • 21
  • 160
  • 208
  • 1
    Thanks for the answer +1. I agree with your architectural observations whole heartedly; but sometimes you play the hand you're dealt. IdentityModel's `AuthenticationHandler` is implemented as a Message Handler. An invalid token stops processing and returns an HTTP 401. This is perfect for every situation...**except** for when you want an exemption for the method that issues valid tokens (assuming one is self issuing, instead of using a 3rd party service). – EBarr Jul 03 '12 at 15:31
  • Best is to talk to Dominick - he is very open to suggestions when it fits the product. I have not yet looked at it in depth but need to pick up soon. – Aliostad Jul 03 '12 at 15:36
  • Agreed - we've been going back and forth, and I'm crafting another email to him on the topic. I was looking for an alternative, to make integrating the changes less disruptive. BTW ...he's started showing up on SO a bit - http://stackoverflow.com/users/672453/leastprivilege – EBarr Jul 03 '12 at 15:40