[
https://issues.apache.org/jira/browse/OFBIZ-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255508#comment-14255508
]
Scott Gray commented on OFBIZ-5035:
-----------------------------------
It looks like this problem popped up because of the introduction of the
CatalogUrlFilter and ContentUrlFilter.
The filters access the parameter map before the code in the RequestHandler gets
the opportunity to set the request's character encoding to UTF-8, once the
parameters are parsed on first access setting the character encoding afterwards
has no effect. Because these filters are mapped to all path requests they also
affect the normal /control/ path, which wouldn't have had this issue prior to
their introduction.
We need to find somewhere very early in the request handling to set character
encoding to UTF-8. We can either add tomcat's SetCharacterEncodingFilter to
all of the web.xml files or we can add similar code to the ContextFilter and
ensure it is always the first filter to run.
> Special characters (latin, accent ...) are in error from an input (search,
> contact us ...)
> ------------------------------------------------------------------------------------------
>
> Key: OFBIZ-5035
> URL: https://issues.apache.org/jira/browse/OFBIZ-5035
> Project: OFBiz
> Issue Type: Bug
> Components: specialpurpose/ecommerce
> Affects Versions: Trunk
> Environment: trunk-r1384251
> Reporter: Eric de Maulde
> Priority: Minor
>
> When a user tapes a special character on a search field or a contact us
> field, OFBiz sends back a wrong character.
> Try on : http://demo-trunk.ofbiz.apache.org/ecommerce
> This error doesn't appear on old stable version : 10.04 & 09.04
> http://demo-stable.ofbiz.apache.org/ecommerce
> http://demo-old.ofbiz.apache.org/ecommerce
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
