Facilities/Wcf/Castle.Facilities.WcfIntegration.Demo/Web.config

   1 <?xml version="1.0"?>
   2
   3 <configuration>
   4
   5         <appSettings/>
   6         <connectionStrings/>
   7
   8         <system.serviceModel>
   9                 <bindings>
  10                 </bindings>
  11                 <client>
  12                         <endpoint address="http://localhost:27197/UsingWindsor.svc"
  13                                           binding="basicHttpBinding"
  14                                   contract="Castle.Facilities.WcfIntegration.Demo.UsingWindsorSvc.IAmUsingWindsor"
  15                                   name="WSHttpBinding_IAmUsingWindsor">
  16                         </endpoint>
  17                 </client>
  18                 <services>
  19                         <!-- Before deployment, you should remove the returnFaults behavior configuration to avoid disclosing information in exception messages -->
  20                         <service name="Castle.Facilities.WcfIntegration.Demo.UsingWindsor">
  21                                 <endpoint contract="Castle.Facilities.WcfIntegration.Demo.IAmUsingWindsor"
  22                                                   binding="basicHttpBinding"/>
  23                         </service>
  24                 </services>
  25         </system.serviceModel>
  26
  27         <system.web>
  28                 <!--
  29             Set compilation debug="true" to insert debugging
  30             symbols into the compiled page. Because this
  31             affects performance, set this value to true only
  32             during development.
  33         -->
  34                 <compilation debug="true" />
  35                 <!--
  36             The <authentication> section enables configuration
  37             of the security authentication mode used by
  38             ASP.NET to identify an incoming user.
  39         -->
  40                 <authentication mode="Windows" />
  41                 <!--
  42             The <customErrors> section enables configuration
  43             of what to do if/when an unhandled error occurs
  44             during the execution of a request. Specifically,
  45             it enables developers to configure html error pages
  46             to be displayed in place of a error stack trace.
  47
  48         <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
  49             <error statusCode="403" redirect="NoAccess.htm" />
  50             <error statusCode="404" redirect="FileNotFound.htm" />
  51         </customErrors>
  52         -->
  53         </system.web>
  54 </configuration>