Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ErrorFilterModule does not filter under medium trust in v1.0.8922 (BETA1) #8

Closed
GoogleCodeExporter opened this issue Sep 14, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Add the ErrorLogModule to the configuration.
2. Add the ErrorFilterModule to the configuration.
3. Add error filtering via configuration that uses data-binding.
4. Cause an error to occur that should be filtered.

What is the expected output? 
The error should not be logged by the error logging module.

What do you see instead?
The error is logged by the error logging module and an exception occurs 
during the binding of the data expression that is swallowed by ASP.NET.

Original issue reported on code.google.com by azizatif on 25 Jun 2007 at 9:34

@GoogleCodeExporter
Copy link
Author

This bug was caused by the fact that ErrorFilterModule.AssertionHelperContext 
was 
marked internal rather than public. Consequently, medium trust applications 
would 
not be able to use any data-bound assertions on the helper context due to 
insufficient permissions. Apply the attached patch to ELMAH sources fix the 
problem.

Original comment by azizatif on 25 Jun 2007 at 9:50

  • Changed state: Fixed

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant