The following reply was made to PR config/3244; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Randy Jae Weinstein <[EMAIL PROTECTED]> Cc: Apache bugs database <[EMAIL PROTECTED]> Subject: Re: config/3244: Inability to customize error 500 Date: Mon, 19 Oct 1998 11:27:34 -0700 (PDT) On Mon, 19 Oct 1998, Randy Jae Weinstein wrote: > Sorry about opening another report, I was unaware you could add to a > closed report. I guess you can though. > > As for the subject, it should have read "Inability to customize error > 403", my mistake (kinda tired here). > > This report is different. Let me explain. Error 500 inability to > customize was do to an error in the htaccess file of a subdirectory. If > the child subdir's htaccess had an error than the standard error message > would be shown. > > The Error 403 has to do with a directory being not set as world read (done > on purpose), and then having a default error message instead of the custom > error message. The 500 Error was fixed do to a change in the later > htaccess file (way it was readin/parsed, I assume), where as the 403 deals > with a directory parsing getting halted. If you had read the response to your previous PR, you would know that the real problem is that when doing merging of directives as walking down a tree, the merge was not "completed" until the entire tree was read. This means that if it aborted in the middle, due to an invalid htaccess file entry, a directory it couldn't read, etc. then the settings higher up the tree wouldn't be used. That was fixed. > > > If indeed the 500 error fix corrects the 403 error fix, then by all means > delete this PR, however I don't think that is the case. > > -Cheers, > RJW > >
