RE: error-page status codes broken, no response to bugzilla report

>The key issue is that declaring an handler ***replaces*** the >standard container behavior; it doesn't ***augment*** it. > >Consider, for example, a webapp that want to implement something like what >the "Redirect" configuration parameter does for Apache (so that old URLs >still work). In today'

RE: error-page status codes broken, no response to bugzilla report

On Thu, 2 Jan 2003, Donald Ball wrote: > Date: Thu, 02 Jan 2003 12:49:40 -0500 > From: Donald Ball <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > To: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: RE: erro

RE: error-page status codes broken, no response to bugzilla report

On 1/2/2003 at 9:23 AM Craig R. McClanahan wrote: >> Nonetheless, I think the patched behavior is much more correct than the >> current behavior and should be applied to cvs. >> > >(Sorry for being out of touch earlier -- holidays and busyness and such). > >I do not agree with the assertion that t

RE: error-page status codes broken, no response to bugzilla report

On Thu, 2 Jan 2003, Donald Ball wrote: > Date: Thu, 02 Jan 2003 10:26:10 -0500 > From: Donald Ball <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: RE: error-page status codes b

RE: error-page status codes broken, no response to bugzilla report

On 12/23/2002 at 9:40 AM Costin Manolache wrote: >It is on my todo list ( I also need this to work, at least for 500 ). >Do you have a patch ? I have attached an erstwhile patch to the bug in bugzilla. It assumes the content type of the error-page resource to be text/html and uses rd.include inst

RE: error-page status codes broken, no response to bugzilla report

On 12/23/2002 at 9:40 AM Costin Manolache wrote: >It is on my todo list ( I also need this to work, at least for 500 ). >Do you have a patch ? not yet, but i'll be happy to work on one for 4.1.x. thanks for taking the time to respond. - donald -- To unsubscribe, e-mail:

RE: error-page status codes broken, no response to bugzilla report

It is on my todo list ( I also need this to work, at least for 500 ). Do you have a patch ? Costin Donald Ball wrote: > Are any tomcat developers going to express any interest in this issue? I > frankly consider being completely ignored to be quite rude and a poor way > to interact with the at-l

RE: error-page status codes broken, no response to bugzilla report

Are any tomcat developers going to express any interest in this issue? I frankly consider being completely ignored to be quite rude and a poor way to interact with the at-large developer community. - donald On 12/19/2002 at 12:13 PM Donald Ball wrote: >On 12/19/2002 at 4:02 PM Martin Algesten wr

RE: error-page status codes broken, no response to bugzilla report

On 12/19/2002 at 4:02 PM Martin Algesten wrote: >The problem with this bug is that there are people here who don't agree >it is a bug... which is just plain ignorant and stupid... THIS IS A >BUGIT NEEDS FIXING! Thank you - now I at least know that other people have observed this behavior and

RE: error-page status codes broken, no response to bugzilla report

they will just ignore you until you go away. Martin > -Original Message- > From: Donald Ball [mailto:[EMAIL PROTECTED]] > Sent: 19 December 2002 15:55 > To: [EMAIL PROTECTED] > Subject: Fwd: error-page status codes broken, no response to > bugzilla report > &g

Fwd: error-page status codes broken, no response to bugzilla report

What does one have to do to get a response to a bug report around here? I submitted it to bugzilla, I followed up here. If it's a bug, I'm happy to help patch. If I'm an idiot, I'd appreciate being told so. - donald On 12/18/2002 at 1:00 PM Donald Ball <[EMAIL PROTECTED]> wrote: >I submitted thi

error-page status codes broken, no response to bugzilla report

I submitted this bug report a few days ago: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15406 It seems to me that tomcat is doing the wrong thing when it tags the error page contents with status code 200 instead of the actual error status code. If this is the case, is anyone interested in f