On 08/27/2012 05:04 PM, Rick Mann wrote:
Oh, I can also put that empty page directive at the end of my include file,
and it also triggers the correct behavior.
What, exactly isn't working? The parsing of the page? Or the
content-type header?
I just created a filter and JSP to reproduce this,
] On Behalf Of Rick Mann
Sent: Tuesday, August 28, 2012 3:50 PM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] JSP encoding issues
Sorry, I should've been more clear.
The problem I'm experiencing is not that the headers aren't being properly
set. It's
Message-
From: resin-interest-boun...@caucho.com [mailto:resin-interest-
boun...@caucho.com] On Behalf Of Rick Mann
Sent: Tuesday, August 28, 2012 3:50 PM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] JSP encoding issues
Sorry, I should've been more
I'm trying to serve everything UTF-8. To this end, I wrote a request filter
that sets the input and output encodings to UTF-8, and I've used that
successfully in the past. I've been able to avoid putting a page encoding
directive in each page.
With resin 4.0.30, I'm seeing something odd. I
Oh, I can also put that empty page directive at the end of my include file, and
it also triggers the correct behavior.
On Aug 27, 2012, at 16:39 , Rick Mann rm...@latencyzero.com wrote:
I'm trying to serve everything UTF-8. To this end, I wrote a request filter
that sets the input and output
