Change elmah NuGet package to add <security allowRemoteAccess="0" /> to <elmah> element

GoogleCodeExporter commented 8 years ago

What new or enhanced feature are you proposing?
A change to the NuGet elmah package.

What goal would this enhancement help you achieve?
Without that element, people who get 403s from remote site after deployment 
when trying to run elmah.axd have to do a lot of searching to figure out what 
the problem is.  If this line were in the Web.config, it would be immediately 
obvious, and the default would still be no remote access.

Original issue reported on code.google.com by tom9...@msn.com on 16 Sep 2011 at 9:23

GoogleCodeExporter commented 8 years ago

Original comment by jamesdriscoll71 on 19 Feb 2012 at 11:57

Changed state: Accepted

GoogleCodeExporter commented 8 years ago

Original comment by jamesdriscoll71 on 19 Feb 2012 at 12:34

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

Original comment by jamesdriscoll71 on 13 Apr 2012 at 11:09

Added labels: Milestone-Release1.2SP2

martinjt / elmah

Change elmah NuGet package to add <security allowRemoteAccess="0" /> to <elmah> element #253