pp wrote: > > midgard-pageresolve will at least tell you whether you can access the > > database at all. I just tested the fix to mgd_auth_midgard, BTW. Before > > the fix I had a 100% failure rate, after the fix 100% success (1000 > > requests in succession). So it seems like it's fixed, but I can't > > reproduce the randomness. > > as I wrote midgard-pageresolve works with new midgard-root file > which is not working on no-MMP midgard. > The problem was with MidgardDatabase and MidgardAuthDatabase. > I need to have two directives per host to get midgard working.
It is very unlikely that you need (or indeed want) MidgardAuthDatabase. It is related to MultiDB which hasn't seen al that much real-world use, and even then only in very specific circumstances. Syntax: MidgardAuthDatabase [database] [username] [password] Example: MidgardAuthDatabase midgardadmin midgard midgard The database to authenticate from. You can use this to arrange access to sites served from databases where you have no Midgard user account. Used in combination with MidgardPageDatabase and MidgardDatabase. Users authenticated from this database will be granted full (root-level) access no matter what. so I can imagine this screwing up auth behaviour. At this moment, you probably want to remove MidgardPageDatabase and MidgardAuthDatabase directives from your apache config. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
