http://blog.palehorse.net/2009/09/29/using-an-external-config-file-with-log4net-with-asp-net-2-0-and-iis7/ Thoughts from a mind twisted by tech and sports Thu, 27 Oct 2011 23:52:26 +0000 hourly 1 http://wordpress.com/ http://blog.palehorse.net/2009/09/29/using-an-external-config-file-with-log4net-with-asp-net-2-0-and-iis7/#comment-3697 Tue, 27 Apr 2010 21:32:09 +0000 http://palehorse.wordpress.com/2009/09/29/using-an-external-config-file-with-log4net-with-asp-net-2-0-and-iis7/#comment-3697 This sounds strange… I mean it is my own code, in global.asax which has not enough rights to read my log4net.config file..? I mean, I’m not in the role of a client from the internet who is trying to access the log4net.config file. But maybe you are right and this is a absolutely volitional behaviour. However this post leads me to the right way. You made my day, thank you so much…

]]> http://blog.palehorse.net/2009/09/29/using-an-external-config-file-with-log4net-with-asp-net-2-0-and-iis7/#comment-3695 Tue, 27 Apr 2010 16:22:22 +0000 http://palehorse.wordpress.com/2009/09/29/using-an-external-config-file-with-log4net-with-asp-net-2-0-and-iis7/#comment-3695 From what I can ascertain, IIS protects all .config files from being read by default. Only files that show up in the filter section are allowed, therefore any .config files that are not standard need to be added there. I also believe this is only an issue if the web is running in pipleline mode, but I’m not certain about that. It seems (my best guess) that it’s simply another layer of security to avoid having sensitive configuration information leaked.

]]> http://blog.palehorse.net/2009/09/29/using-an-external-config-file-with-log4net-with-asp-net-2-0-and-iis7/#comment-3694 Tue, 27 Apr 2010 15:57:35 +0000 http://palehorse.wordpress.com/2009/09/29/using-an-external-config-file-with-log4net-with-asp-net-2-0-and-iis7/#comment-3694 Thanks you for this information. Instead of defining any request filter i’ve putted the config file in a separate directory. The security settings are defined, that nobody can access that directory. One thing i don’t understand: why isn’t it possible to read the config file when the name is log4net.config…? I’m realy confused about that behaviour…

]]>