[
https://issues.apache.org/jira/browse/OFBIZ-13333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Malin updated OFBIZ-13333:
----------------------------------
Summary: Bad request parameter encoding with tomcat 9 (was: bad request
parameter encoding )
> Bad request parameter encoding with tomcat 9
> --------------------------------------------
>
> Key: OFBIZ-13333
> URL: https://issues.apache.org/jira/browse/OFBIZ-13333
> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: 24.09.04
> Reporter: Nicolas Malin
> Priority: Major
> Attachments: Capture d’écran du 2025-12-30 11-29-25.png, Capture
> d’écran du 2025-12-30 11-29-41.png
>
>
> Hello,
> I'm in front of a strange issue with parameter encoding.
> On demo-trunk and demo-stable, if you create a new workEfffort from standard
> from (not from modal with json call), parameters haven't well decoded and if
> you have a special case the value isn't correct.
> Example on workEffortName you set a french work *Génial* and OFBiz store
> *Génial*
> After some research, I saw that tomcat 9 add a [new system to parse
> URI|https://cwiki.apache.org/confluence/display/TOMCAT/Character+Encoding#CharacterEncoding-Q3]
> sent with content-type : {{application/x-www-form-urlencoded}} [1]
> We can set element
> *<request-character-encoding>UTF-8</request-character-encoding>* on web.xml.
> I added it locally on workeffort/web.xml and I confirm this solve the problem.
>
> But interrogation from my side, do we need add this to all webapp, or someone
> have a better vision on this subject and know a better fix ?
>
> [1]
> https://cwiki.apache.org/confluence/display/TOMCAT/Character+Encoding#CharacterEncoding-Q3
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
