It might make more sense, however its been working this way for so many years, I hesistate to change the behavior at this point. From a development perspective, having it output 200 status is easiest because Apache will render that code no problem, otherwise one might have to start dealing with error document rendering & that kind of thing.
Regards, Josh Quoting Philip Mak <[EMAIL PROTECTED]>: > On Fri, Jul 18, 2003 at 10:24:20PM -0400, Joshua Chamas wrote: > > This is what happens when Debug is set to higher than 1/-1. You > > might have settings of 2/-2 or 3/-3, which renders errors pretty > > HTML format like this. > > Wouldn't it make more sense for the server to return an HTTP code of > 500 (and still display the error on the screen)? This way, > applications that call the ASP script and rely on seeing an HTTP error > code to know if something is wrong will not be fooled. Website status > monitoring applications are another thing that may think all is well > if they see HTTP 200 OK. I use "Debug 2" sometimes even in production > environments. > > I know there are some browsers that don't display HTTP 500 code > messages sometimes, but only when they are under 512 bytes long, and > all Apache::ASP error pages would be more than that length I think. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
