Re: RequestProcessor and contentType response header

2009-06-21 Thread Avlesh Singh
> > I would recomend upgrading to a later version of struts > Oh Mike, I wish I could do that! :) For the problem at hand, I am better off sub-classing the RequestProcessor. Having said that, would still try and upgrade asap. Cheers Avlesh On Mon, Jun 22, 2009 at 9:30 AM, Mike Dave wrote: > >

Re: RequestProcessor and contentType response header

2009-06-21 Thread Mike Dave
> > Sounds counter-intuitive. Why should the RequestProcessor overwrite? > I am in agreement with you, Avlesh. This behaviour is erratic. I would recomend upgrading to a later version of struts assuming that the behaviour has been fixed. -m- On Sun, Jun 21, 2009 at 8:46 PM, Avlesh Singh wrote: >

Re: RequestProcessor and contentType response header

2009-06-21 Thread Avlesh Singh
> > It's also the weekend. I truly respect that. It's not a bug, that's just how it works. > Sounds counter-intuitive. Why should the RequestProcessor overwrite? Overriding the request processor is the normal way to add behavior to apps > running that version of Struts. > Thanks for approving th

Re: RequestProcessor and contentType response header

2009-06-21 Thread Dave Newton
Avlesh Singh wrote: Did not get a response yet :( It's also the weekend. Is this a dev list question No. 1. Shouldn't this method also check if the response already has a contentType header applied or not? Is this a known bug, or am I missing something? It's not a bug, that's j

Re: RequestProcessor and contentType response header

2009-06-21 Thread Avlesh Singh
Did not get a response yet :( Is this a dev list question or my assumptions are correct? Cheers Avlesh On Sat, Jun 20, 2009 at 8:21 PM, Avlesh Singh wrote: > I am using Struts 1.2.7 > I wrote a Filter which intercepts all requests and applies response headers > (based on some external configura

RequestProcessor and contentType response header

2009-06-20 Thread Avlesh Singh
I am using Struts 1.2.7 I wrote a Filter which intercepts all requests and applies response headers (based on some external configuration) to it. All response headers applied in my Filter other than "Content-Type" were obeyed and sent to the client. Content-Type was always "text/html". After a lot