in the filter (IFilter), the Execute methods accepts IEngineContext, which has a reference to the current IRequest
so context.Request.Headers should also work, and keep the IFilter more testable (as it won't be coupled with HttpContext.Current) On Fri, Oct 17, 2008 at 9:32 PM, Gabriel Mancini de Campos < [EMAIL PROTECTED]> wrote: > > thanks victor! > > in your filter > > if you use jQuery and you need to know if your request is a ajax > process or a form process use this :D > > bool ajax = (System.Web.HttpContext.Current.Request.Headers["X- > Requested-With"] == "XMLHttpRequest"); > > see u guys > > > > On Oct 17, 4:29 pm, "Victor Kornov" <[EMAIL PROTECTED]> wrote: > > No, it should not change from browser to browser. The headers is setup by > > jQuery. > > > > On Fri, Oct 17, 2008 at 11:21 PM, Gabriel Mancini de Campos < > > > > [EMAIL PROTECTED]> wrote: > > > > > Hi Ken > > > > > I found this, but this header don't change of browser to other ? > > > example, the object is diferent between ie and ff. > > > -- Ken Egozi. http://www.kenegozi.com/blog http://www.musicglue.com http://www.castleproject.org http://www.gotfriends.co.il --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
