I can't think of another case - but there could be one. The simplest way to produce this problem is just turn some kind of auth on in <Location /> - then the 401 error document will be protected and you will get an error within ap_die -
sterling On Tue, 13 Nov 2001, Justin Erenkrantz wrote: > On Tue, Nov 13, 2001 at 01:47:01PM -0500, Cliff Woolley wrote: > > If we're willing to touch the tarball at all, a less obtrusive change > > might be to just comment out the .html.var line for ErrorDocument 401 in > > the default config file, which also fixes (works around) the problem (I > > tested it). But I'm also willing to just document in the release notes > > that if you want to use mod_auth, you need to comment that line out for > > now. > > Wouldn't anything that calls ap_die be affected? Or, am I > misunderstanding this bug? > > I don't care much as the problem is fixed in HEAD, so at the > very least, we can include the diff in the release notes. > > I'm not sure what the ErrorDocument 401 has to do with this, but > I didn't really understand how to reproduce this bug. -- justin > >
