1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134

<?xml version="1.0" encoding="utf-8"?>
<configuration>

    <configSections>
        <sectionGroup name="elmah">
            <!-- The requirePermission="false" attributes on section
                 elements below are only needed for partially trusted 
                 applications in ASP.NET 2.0 and later. -->
            <section name="security" requirePermission="false" type="Elmah.SecuritySectionHandler, Elmah"/>
            <section name="errorLog" requirePermission="false" type="Elmah.ErrorLogSectionHandler, Elmah" />
            <section name="errorMail" requirePermission="false" type="Elmah.ErrorMailSectionHandler, Elmah" />
            <section name="errorFilter" requirePermission="false" type="Elmah.ErrorFilterSectionHandler, Elmah"/>
            <section name="errorTweet" requirePermission="false" type="Elmah.ErrorTweetSectionHandler, Elmah"/>
        </sectionGroup>
    </configSections>

    <elmah configSource="elmah.config" />
    
    <system.web>

        <httpModules>
            
            <!-- 
                Uncomment the entry below if all of the following are true: 
                1) you are using wildcard mapping in IIS 5.x
                2) you are not using .Net 1.0
                3) you are experiencing http 404 errors when trying to view
                   elmah.axd or elmah.axd/detail?id=* etc
            -->
            <!--<add name="FixIIS5xWildcardMapping" type="Elmah.FixIIS5xWildcardMappingModule, Elmah"/>-->

            <!-- 
                Uncomment the entry below if you are using MS Ajax v1.0.x.x
                and want to capture errors during Partial Postbacks
                NB This is not required for the version of Ajax shipped with .Net Framework v3.5!
            -->
            <!--<add name="MsAjaxDeltaErrorLog" type="Elmah.MsAjaxDeltaErrorLogModule, Elmah"/>-->

            <add name="ErrorLog" type="Elmah.ErrorLogModule, Elmah"/>
        
            <!-- 
                Uncomment the entries below if error mail reporting 
                and filtering is desired.
            -->
            
            <!--<add name="ErrorMail" type="Elmah.ErrorMailModule, Elmah" />-->
            <!--<add name="ErrorFilter" type="Elmah.ErrorFilterModule, Elmah"/>-->
            <!--<add name="ErrorTweet" type="Elmah.ErrorTweetModule, Elmah"/>-->

        </httpModules>
        
        <httpHandlers>

            <!-- 
                This entry provides the UI for the error log at
                elmah.axd below the application path. For example,
                if your domain is www.example.com and your application
                is at the root, then you can view the error log by
                visiting the following URL:
                
                http://www.example.com/elmah.axd
                
                IMPORTANT! To secure this location, consult the
                following notes:
                
                http://code.google.com/p/elmah/wiki/SecuringErrorLogPages
            -->
            
            <add verb="POST,GET,HEAD" path="elmah.axd" type="Elmah.ErrorLogPageFactory, Elmah" />
        
        </httpHandlers>
       
    </system.web>

    <!-- 
        The <system.webServer> section is required for running ELMAH under Internet
        Information Services 7.0. It is not necessary for previous version of IIS.
        
        In general, it would be best to include it for all .NET Framework 2.0 and above
        configurations in order to have a more portable solution between various
        versions of IIS.

        IIS 5.x, IIS 6 require the modules and handlers to be declared in <system.web>
        whereas IIS 7 needs them declared here and complains if they are in fact
        declared in <system.web>. Fortunately, the
        <validation validateIntegratedModeConfiguration="false" /> entry tells IIS 7 
        not to worry about the modules and handlers declared in <system.web>.
        
        If you only ever want to use IIS 7, then do the following:
        
        1. Remove handlers and modules from <system.web>
        2. Remove the <validation validateIntegratedModeConfiguration="false" /> element
    -->
    <!--

    <system.webServer>
        <validation validateIntegratedModeConfiguration="false" />
        <modules>
            <add name="ErrorLog" type="Elmah.ErrorLogModule, Elmah" preCondition="managedHandler" />
            <add name="ErrorFilter" type="Elmah.ErrorFilterModule, Elmah" preCondition="managedHandler" />
            <add name="ErrorMail" type="Elmah.ErrorMailModule, Elmah" preCondition="managedHandler" />
            <add name="ErrorTweet" type="Elmah.ErrorTweetModule, Elmah" preCondition="managedHandler" />
        </modules>
        <handlers>
            <add name="Elmah" path="elmah.axd" verb="POST,GET,HEAD" type="Elmah.ErrorLogPageFactory, Elmah" preCondition="integratedMode" />
        </handlers>
    </system.webServer>

    -->

    <!-- 
        The following entry denies unauthenticated users access to 
        the path from where ELMAH's handlers are accessible. If you 
        have role-based security implemented, you SHOULD consider 
        instead allowing access by a particular role (for example, 
        operators and administrators).
        
        IMPORTANT: If you change the path of the handler above
        then you MUST also change the path in the location tag below
        to be the same.

        For more information, see:
        http://code.google.com/p/elmah/wiki/SecuringErrorLogPages
    -->

    <location path="elmah.axd">
        <system.web>
            <authorization>
                <deny users="?"/>
            </authorization>
        </system.web>
    </location>

</configuration>