ake the difference).
>
> Aaron
>
>
>> -Original 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 th
> 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 clear.
>
> The problem I'm experienc
On Aug 28, 2012, at 14:29 , Scott Ferguson wrote:
> On 08/28/2012 01:50 PM, Rick Mann wrote:
>> Sorry, I should've been more clear.
>>
>> The problem I'm experiencing is not that the headers aren't being properly
>> set. It's that UTF-8 in my source page is getting mangled. In this case, a
>>
On 08/28/2012 01:50 PM, Rick Mann wrote:
> Sorry, I should've been more clear.
>
> The problem I'm experiencing is not that the headers aren't being properly
> set. It's that UTF-8 in my source page is getting mangled. In this case, a
> copyright symbol (©), while still rendered in the page, is p
Sorry, I should've been more clear.
The problem I'm experiencing is not that the headers aren't being properly set.
It's that UTF-8 in my source page is getting mangled. In this case, a copyright
symbol (©), while still rendered in the page, is preceded by a capital A with
an accent (not sure o
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
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 wrote:
> 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,
