J.Patterson Waltz III writes:
> Yep. That was it.
> I commented out the filter definition for ResponseOverrideFilter and
> everything displayed as expected.
> I then reinstated it, placing it *after* the
> SetCharacterEncodingFilter in web.xml, and all was still well.
Great!
> Really, really a
On 6 janv. 05, at 18:13, Guillaume Cottenceau wrote:
I also have another filter, the ResponseOverrideFilter used by
displaytag, which appears before the SetCharacterEncodingFilter in my
web.xml. I wonder if it could be interfering with the
SetCharacterEncodingFilter?
Yes, if it reads the request pa
J.Patterson Waltz III writes:
> On 6 janv. 05, at 17:44, Guillaume Cottenceau wrote:
>
> > J.Patterson Waltz III writes:
> >
> >> Notice in the third line of the form data:
> >> &personTO.comments=%C3%A9t%C3%A9
> >> That's 'été' URLencoded as UTF-8.
> >>
> >> So I'm still stumped. :-(
> >
> > B
On 6 janv. 05, at 17:44, Guillaume Cottenceau wrote:
J.Patterson Waltz III writes:
Notice in the third line of the form data:
&personTO.comments=%C3%A9t%C3%A9
That's 'été' URLencoded as UTF-8.
So I'm still stumped. :-(
But that's exactly what you want. The SetCharacterEncodingFilter
will set the c
J.Patterson Waltz III writes:
> Notice in the third line of the form data:
> &personTO.comments=%C3%A9t%C3%A9
> That's 'été' URLencoded as UTF-8.
>
> So I'm still stumped. :-(
But that's exactly what you want. The SetCharacterEncodingFilter
will set the character encoding of the HttpServletRequ
On 6 janv. 05, at 17:17, Guillaume Cottenceau wrote:
J.Patterson Waltz III writes:
On 6 janv. 05, at 15:52, J.Patterson Waltz III wrote:
Now, I guess I'll just have to try using the character encoding
filter Guillaume recommended.
Ack! I'm about to pull my hair out over these encoding issues. I a
J.Patterson Waltz III writes:
> On 6 janv. 05, at 15:52, J.Patterson Waltz III wrote:
> >
> >
> > Now, I guess I'll just have to try using the character encoding
> > filter Guillaume recommended.
>
> Ack! I'm about to pull my hair out over these encoding issues. I added
> the SetCharacterEncodin
On 6 janv. 05, at 15:52, J.Patterson Waltz III wrote:
Now, I guess I'll just have to try using the character encoding filter
Guillaume recommended.
Ack! I'm about to pull my hair out over these encoding issues. I added
the SetCharacterEncodingFilter from the Tomcat 5 distribution to my web
appl
On 5 janv. 05, at 13:30, J. Patterson Waltz III wrote:
in article [EMAIL PROTECTED], Josh Cronemeyer at [EMAIL PROTECTED]
wrote
on 4/01/05 18:02:
J. Patterson Waltz III wrote:
Merci Guillaume,
I had actually seen the references to the Filter solution in the
comments of
Struts bug 16191 in Bugzil
in article [EMAIL PROTECTED], Josh Cronemeyer at [EMAIL PROTECTED] wrote
on 4/01/05 18:02:
> J. Patterson Waltz III wrote:
>
>> Merci Guillaume,
>>
>> I had actually seen the references to the Filter solution in the comments of
>> Struts bug 16191 in Bugzilla:
>> http://issues.apache.org/bugzill
"J. Patterson Waltz III" writes:
> P.S. - I know how to view the headers of replies sent from the server to the
> browser, but am not sure how to get at those sent from the browser to the
> server, to make sure that they are indeed UTF-8. Any suggestions?
I usually temporarily modify the URL whe
J. Patterson Waltz III wrote:
Merci Guillaume,
I had actually seen the references to the Filter solution in the comments of
Struts bug 16191 in Bugzilla:
http://issues.apache.org/bugzilla/show_bug.cgi?id=16191
I will try that out and see if it improves my results.
I remain perplexed at what changes
Merci Guillaume,
I had actually seen the references to the Filter solution in the comments of
Struts bug 16191 in Bugzilla:
http://issues.apache.org/bugzilla/show_bug.cgi?id=16191
I will try that out and see if it improves my results.
I remain perplexed at what changes between versions 1.1 and 1
"J. Patterson Waltz III" writes:
> Hello,
>
> I recently upgraded a J2EE/Struts web application I'm working on to the
> 1.2.4 version of Struts, and ever since I made this change, I've been
> encountering a problem with the encoding of non-ascii character data
> submitted in forms. All my pages
Hello,
I recently upgraded a J2EE/Struts web application I'm working on to the
1.2.4 version of Struts, and ever since I made this change, I've been
encountering a problem with the encoding of non-ascii character data
submitted in forms. All my pages are set to use UTF-8 encoding (via a <%@
page p
15 matches
Mail list logo
