Bug 724764 (BRMS-602)

Summary: Add URIEncoding attribute in BRMS-standalone EWP server.xml for multibyte characters WebDAV issue
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Toshiya Kobayashi <tkobayas>
Component: BRM (Guvnor), ConfigurationAssignee: Julian Coleman <jcoleman>
Status: VERIFIED --- QA Contact: Lukáš Petrovický <lpetrovi>
Severity: unspecified Docs Contact:
Priority: low    
Version: 5.1.0 GACC: atangrin, jcoleman, lpetrovi, manstis, rwagner, tkobayas
Target Milestone: ER1   
Target Release: BRMS 5.3.1 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-602
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
JBoss Enterprise BRMS supports any UTF-8 character as part of a rule name, but when using WebDAV access, the multibyte characters in the URL were decoded as ISO-8859-1 by default. This has been resolved by adding URIEncoding support.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Toshiya Kobayashi 2011-06-08 09:08:17 UTC
Affects: Compatibility/Configuration, Release Notes
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007BhZE&sfdc.override=1
securitylevel_name: Public

Drools/Guvnor supports any UTF-8 character as part of rule name, but when using WebDAV access, the multibyte characters in the URL are decoded as ISO-8859-1 by default. It will end up with 404.

You can work around it by adding URIEncoding attribute in Connector settings in server.xml.

{noformat}
      <Connector protocol="HTTP/1.1" port="8080" address="${jboss.bind.address}" 
               connectionTimeout="20000" redirectPort="8443" URIEncoding="UTF-8" />
{noformat}

Here is a knowledgebase article for this issue.
https://access.redhat.com/kb/docs/DOC-57339

It would be nice to have the settings in brms-standalone EWP out-of-the-box.

Comment 1 Toshiya Kobayashi 2011-06-08 09:09:37 UTC
Link: Added: This issue is related to BRMS-601


Comment 2 Toshiya Kobayashi 2011-06-08 09:17:56 UTC
I raised BRMS-601 for documentation. Hmm, I'm a bit unsure if I should have combine them into one JIRA :(

Comment 3 Rick Wagner 2011-08-25 19:22:52 UTC
GSS prioritizes 'low'.  Customer isn't stuck, workaround is documented.

Comment 4 lcarlon 2011-08-29 02:15:24 UTC
Toshiya,

please continue to open separate documentation bugs whenever necessary :)

Thanks
Lee

Comment 5 Zuzana Krejčová 2012-07-09 10:47:27 UTC
Could we add the attribute to Connector elements in the server.xml by default? It seems better to do it. 
If not, could we close this bug, as it's been documented already?

Comment 6 lcarlon 2012-07-13 06:15:51 UTC
It is documented in the User Guide.

Comment 8 manstis 2012-08-29 12:27:24 UTC
Nothing for dev to do on this one :)

Comment 9 Prakash Aradhya 2012-08-30 15:09:34 UTC
Looks like the issue still persists in EAP.. Productization team would own this

Comment 11 Julian Coleman 2012-09-03 16:20:35 UTC
Resolved with revision 11414 of:

  brms-p/src/main/patches/eap/patch_add_uriencoding.xml

Commit message:

  BZ-724764
  Add URIEncoding to server/${config}/deploy/jbossweb.sar/server.xml.

Comment 12 Zuzana Krejčová 2012-09-13 12:27:23 UTC
The setting is there in both default and production profiles.

Comment 13 lcarlon 2012-09-13 21:47:20 UTC
Docs note: I've added a note to the user guide stating that manually adding support is only required in versions 5.3 and below. The note will show up the next time we restage the doc.

- Lee

[1]http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html/BRMS_User_Guide/ch07s03.html#WebDav_Unicode