If you're going to call Configure from Application_Start, you should
always have access to the current HttpContext which means you may be
able to wire up the event like this:
// ???
HttpContext.Current.ApplicationInstance.BeginRequest +=
new EventHandler(this.OnPreRequestHandlerExecute);
---
Do you think passing in the current process' credentials as soon as
they are available would solve the problem?
I made a static event on Global called PreRequestHandlerExecute that
gets fired inside of Application_PreRequestHandlerExecute. This
appender subscribes to the event and executes code t
I never tried this because there was no point in my particular case, but the
WindowsSecurityContext documentation says this in the section on the
Credentials property:
" When the mode is set to Process no other properties need to be set. If the
calling thread is impersonating then it will be rever
The app is a web service and it is calling the config code within the
static class constructor, so it is called after the first request but
once before anything happens. That way it does have the correct Identity
but only affects the very first call.
However, it is still the wrong identity, as it
It suddenly occurs to me that if you don't have high traffic volumes you
could do something like:
if (!IsPostBack)
{
}
That is, configure not once application, but once per page per user.
I didn't say it was a great idea, now. I just said you could do it, and I
suppose you would then b
Ah. I see now. I'm afraid you're S.O.L., Colin. (Unless someone else out
there has a better idea?)
You see, you need to be calling that configureandwatch() or configure() only
once per application "session", yes? And for ASP.NET, that point is
Application_Start(), when the web site is brought up.
I saw you previous posts, and see that you had cracked the code for the
securityContext. I tried that and it works great. I was just trying to
take the next step and remove the hard coded username/password from code
or the config - especially since the network admins manage IIS and
passwords, so re
As always, very helpful, Ron. Thanks, that worked.
Just so I'm clear, though ...
If these filters are additive, then why do I get everything if I don't
specify any filter at all? And if they're subtractive, why do I need the
DenyAllFilter at all? Or is there something special about DenyAllFilter?
Yup. Been there, my friend.
I was never completely satisfied with what I found, but it wasn't really
log4net's fault; just security choices that have to be made.
The following code in Application_Start() of Global.asax.cs did indeed do
for me what you're talking about, if I'm understading your re
--- Billy Barnum <[EMAIL PROTECTED]> wrote:
> I'm having trouble making a PropertyFilter work with some custom
> properties
> of mine, and the archives didn't turn up anything. I'm probably not
> understanding what PropertyFiltering is or am fat-fingering
> something; help
> appreciat
I have been have a related problem on this and would appreciate any help
in getting it configured right.
I have 2003/IIS6/ASP.NET application that accesses a remote database.
The application in IIS has its 'anonymous access' user set to a service
account, which has access to some stored procedures
I'm having trouble making a PropertyFilter work with some custom properties
of mine, and the archives didn't turn up anything. I'm probably not
understanding what PropertyFiltering is or am fat-fingering something; help
appreciated.
Expected Behavior: a certain FileAppender named 'AssertionExcepti
Hi,
I'm setting onlyFixPartialEventData=true in my config file and am using an
ADONetAppender (log4net 1.2.8). In my appender config settings I have
parameters for ClassName, MethodName, FileName, and LineNumber, but shouldn't
these be NULL in the database since onlyFixPartialEventData is equal
13 matches
Mail list logo
