Request is not available in this context

Question

I m running IIS 7 Integrated mode and I m getting   Request is not available in this context  when I try to access it in a Log4Net related function that is called from Application Start  This is the line of code I ve   if  HttpContext Current    null  amp  amp  HttpContext Current Request    null    and an exception is being thrown for second comparison    What else can I check other than checking HttpContext Current Request for null      A similar question is posted    Request is not available in this context exception when runnig mvc on iis7 5  but no relevant answer there either

User · Answer

You can use following       protected void Application Start object sender  EventArgs e                ThreadPool QueueUserWorkItem new WaitCallback StartMySystem               private void StartMySystem object state                Log HttpContext Current Request ToString

User · Answer

Please see IIS7 Integrated mode  Request is not available in this context exception in Application Start      The    Request is not available in this   context    exception is one of the more   common errors you may receive on when   moving ASP NET applications to   Integrated mode on IIS 7 0   This   exception happens in your   implementation of the   Application Start method in the   global asax file if you attempt to   access the HttpContext of the request   that started the application

User · Answer

This worked for me - if you have to log in Application Start  do it before you modify the context   You will get a log entry  just with no source  like   2019-03-12 09 35 43 659 INFO   null  - Application Started  I generally log both the Application Start and Session Start  so I see more detail in the next message  2019-03-12 09 35 45 064 INFO    Leads Leads aspx - Session Started  Local           protected void Application Start object sender  EventArgs e                        log4net Config XmlConfigurator Configure                log Info  Application Started                GlobalContext Properties  page     new GetCurrentPage                       protected void Session Start object sender  EventArgs e                        Globals  Environment   WebAppConfig getEnvironment Request Url AbsoluteUri  Properties Settings Default LocalOverride               log Info string Format  Session Started   0     Globals  Environment

User · Answer

Since there s no Request context in the pipeline during app start anymore  I can t imagine there s any way to guess what server port the next actual request might come in on   You have to so it on Begin Session   Here s what I m using when not in Classic Mode  The overhead is negligible        lt summary gt      Class is called only on the first request      lt  summary gt  private class AppStart       static bool  init   false      private static Object  lock   new Object              lt summary gt          Does nothing after first request          lt  summary gt           lt param name  context  gt  lt  param gt      public static void Start HttpContext context                if   init                        return                      create class level lock in case multiple sessions start simultaneously         lock   lock                        if    init                                string server   context Request ServerVariables  SERVER NAME                    string port   context Request ServerVariables  SERVER PORT                    HttpRuntime Cache Insert  basePath    http       server         port                          init   true                                   protected void Session Start object sender  EventArgs e          initializes Cache on first request     AppStart Start HttpContext Current

User · Answer

In visual studio 2012  When I published the solution mistakenly with  debug  option I got this exception  With  release  option it never occurred  Hope it helps

User · Answer

You can get around the problem without switching to classic mode and still use Application Start  public class Global   HttpApplication      private static HttpRequest initialRequest      static Global              initialRequest   HttpContext Current Request                  void Application Start object sender  EventArgs e               access the initial request here        For some reason  the static type is created with a request in its HTTPContext  allowing you to store it and reuse it immediately in the Application Start event

User · Answer

This is very classic case  If you end up having to check for any data provided by the http instance then consider moving that code under the BeginRequest event   void Application BeginRequest Object source  EventArgs e    This is the right place to check for http headers  query string and etc    Application Start is for the settings that apply for the application entire run time  such as routing  filters  logging and so on   Please  don t apply any workarounds such as static  ctor or switching to the Classic mode unless there s no way to move the code from the Start to BeginRequest  that should be doable for the vast majority of your cases

User · Answer

When you have custom logging logic  it is rather annoying to be forced either not to log application start or to have to let an exception occurs in the logger  even if handled    It appears that rather than testing for Request availability  you can test for Handler availability  when there is no Request  it would be strange to still have a request handler  And testing for Handler does not raise that dreaded Request is not available in this context exception   So you may change your code to   var currContext   HttpContext Current  if  currContext    null  amp  amp  currContext Handler    null    Beware  in the context of a http module  Handler may not be defined though Request and Response are defined  I have seen that in BeginRequest event   So if you need request response logging in a custom http module  my answer may not be suitable

User · Answer

Based on OP detailed needs explained in comments  a more appropriate solution exists  The OP states he wishes to add custom data in its logs with log4net  data related to requests   Rather than wrapping each log4net call into a custom centralized log call which handles retrieving request related data  on each log call   log4net features context dictionaries for setting up custom additional data to log  Using those dictionnaries allows to position your request log data for current request at BeginRequest event  then to dismiss it at EndRequest event  Any log in between will benefit from those custom data   And things that do not happen in a request context will not try to log request related data  eliminating the need to test for request availability  This solution matches the principle Arman McHitaryan was suggesting in his answer   For this solution to work  you will also need some additional configuration on your log4net appenders in order for them to log your custom data   This solution can be easily implemented as a custom log enhancement module  Here is sample code for it   using System  using System Web  using log4net  using log4net Core   namespace YourNameSpace       public class LogHttpModule   IHttpModule               public void Dispose                            nothing to free                    private const string  ipKey    IP           private const string  urlKey    URL           private const string  refererKey    Referer           private const string  userAgentKey    UserAgent           private const string  userNameKey    userName            public void Init HttpApplication context                        context BeginRequest    WebAppli BeginRequest              context PostAuthenticateRequest    WebAppli PostAuthenticateRequest                 All custom properties must be initialized  otherwise log4net will not get                them from HttpContext              InitValueProviders  ipKey   urlKey   refererKey   userAgentKey                   userNameKey                      private void InitValueProviders params string   valueKeys                        if  valueKeys    null                  return              foreach var key in valueKeys                                GlobalContext Properties key    new HttpContextValueProvider key                                    private void WebAppli BeginRequest object sender  EventArgs e                        var currContext   HttpContext Current              currContext Items  ipKey    currContext Request UserHostAddress              currContext Items  urlKey    currContext Request Url AbsoluteUri              currContext Items  refererKey    currContext Request UrlReferrer    null                    currContext Request UrlReferrer AbsoluteUri   null              currContext Items  userAgentKey    currContext Request UserAgent                     private void WebAppli PostAuthenticateRequest object sender  EventArgs e                        var currContext   HttpContext Current                 log4net doc states that  identity is  extremely slow                  http   logging apache org log4net release sdk log4net Layout PatternLayout html                So here is some custom retrieval logic for it  so bad  especialy since I                tend to think this is a missed copy paste in that documentation                 Indeed  we can find by inspection in default properties fetch by log4net a                log4net Identity property with the data  but it looks undocumented                currContext Items  userNameKey    currContext User Identity Name                          General idea coming from         http   piers7 blogspot fr 2005 12 log4net-context-problems-with-aspnet html        We can not use log4net ThreadContext or LogicalThreadContext with asp net  since        asp net may switch thread while serving a request  and reset the call context        in the process      public class HttpContextValueProvider   IFixingRequired               private string  contextKey          public HttpContextValueProvider string contextKey                         contextKey   contextKey                     public override string ToString                         var currContext   HttpContext Current              if  currContext    null                  return null              var value   currContext Items  contextKey               if  value    null                  return null              return value ToString                       object IFixingRequired GetFixedObject                         return ToString                        Add it to your site  IIS 7  conf sample    lt system webServer gt     lt  -- other stuff removed     -- gt     lt modules gt       lt  -- other stuff removed     -- gt       lt add name  LogEnhancer  type  YourNameSpace LogHttpModule  YourAssemblyName  preCondition  managedHandler    gt       lt  -- other stuff removed     -- gt     lt  modules gt     lt  -- other stuff removed     -- gt   lt  system webServer gt    And set up appenders to log those additional properties  sample config    lt log4net gt     lt appender name  RollingLogFileAppender  type  log4net Appender RollingFileAppender  gt       lt  -- other stuff removed     -- gt       lt layout type  log4net Layout PatternLayout  gt         lt conversionPattern value   date   thread   -5level  logger -  message -  property newline exception    gt       lt  layout gt     lt  appender gt     lt appender name  SqlAppender  type  log4net Appender AdoNetAppender  gt       lt  -- other stuff removed     -- gt       lt commandText value  INSERT INTO YourLogTable   Date   Thread   Level   Logger   UserName   Message   Exception   Ip   Url   Referer   UserAgent   VALUES   log date   thread   log level   logger   userName   message   exception   Ip   Url   Referer   UserAgent     gt       lt  -- other parameters removed     -- gt       lt parameter gt         lt parameterName value   userName    gt         lt dbType value  String    gt         lt size value  255    gt         lt layout type  log4net Layout PatternLayout  gt           lt conversionPattern value   property userName     gt         lt  layout gt       lt  parameter gt       lt parameter gt         lt parameterName value   Ip   gt         lt dbType value  String    gt         lt size value  255    gt         lt layout type  log4net Layout PatternLayout  gt           lt conversionPattern value   property Ip     gt         lt  layout gt       lt  parameter gt       lt parameter gt         lt parameterName value   Url   gt         lt dbType value  String    gt         lt size value  255    gt         lt layout type  log4net Layout PatternLayout  gt           lt conversionPattern value   property Url     gt         lt  layout gt       lt  parameter gt       lt parameter gt         lt parameterName value   Referer   gt         lt dbType value  String    gt         lt size value  255    gt         lt layout type  log4net Layout PatternLayout  gt           lt conversionPattern value   property Referer     gt         lt  layout gt       lt  parameter gt       lt parameter gt         lt parameterName value   UserAgent   gt         lt dbType value  String    gt         lt size value  255    gt         lt layout type  log4net Layout PatternLayout  gt           lt conversionPattern value   property UserAgent     gt         lt  layout gt       lt  parameter gt     lt  appender gt     lt  -- other stuff removed     -- gt   lt  log4net gt

User · Answer

I was able to workaround hack this problem by moving in to  Classic  mode from  integrated  mode

User · Answer

do this in global asax cs   protected void Application Start         string ServerSoftware   Context Request ServerVariables  SERVER SOFTWARE      string server   Context Request ServerVariables  SERVER NAME      string port   Context Request ServerVariables  SERVER PORT      HttpRuntime Cache Insert  basePath    http       server         port                      works like a charm  this Context Request is there     this Request throws exception intentionally based on a flag

[asp.net] Request is not available in this context

Examples related to asp.net

Examples related to iis-7