Sorry, I was narrowly viewing the question of whether the behavior of the redirect itself was a bug. Since you can successfully call an abort command afterwards, it seems that the bug is not in the redirect itself, but how the mess gets cleaned up after the fact. Namely, it seems, that ADP handler gets freaks out when you've already sent a fully formed response before it gets to do so, and nobody told it not to. It's still a coding error not to inform the ADP that it needn't return a response, but crashing is of course an unacceptable result particularly for such a minor breach of protocol.
-Titi -----Original Message----- From: Daniel P. Stasinski [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 06, 2006 2:50 PM To: AOLSERVER@LISTSERV.AOL.COM Subject: Re: [AOLSERVER] internal server redirects On 9/6/06, Titi Ala'ilima <[EMAIL PROTECTED]> wrote: > It's not a bug, it's a feature. Seriously. Sometimes you want to > return a response to the connection and then continue processing > afterwards. Or at least, sometimes _I_ want to do that. :-) That's exactly why its a bug. You may indeed want to continue processing after sending a response to the client but you can't do that if the server crashes. Daniel -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
