Siebel Is Incorrectly using Java Encoding Instead of URL Encoding for Form Submission HTTP POST Request.
(Doc ID 2725906.1)
Last updated on NOVEMBER 09, 2020
Applies to:Siebel CRM - Version 19.7 and later
Information in this document applies to any platform.
The Siebel application is not encoding certain special characters correctly for HTTP POST requests.
When you do common task in the application such as entering a record or performing a query on an applet, there is a HTTP POST request that is sent from the client to the server. It was observed that when you enter certain special characters, it is not encoding the characters correctly. It appears that the application is using Java encoded characters instead of the expected URL encoding.
Some examples of special characters that were observed with issues are below. Users may potentially copy text from applications such as Microsoft Word and paste it to a Siebel field with these special characters:
You can see the POST request by using some network tools such as a network sniffer or the browsers "Developer Tools" to see the parameters that are sent in the request. For instance, the 'En Dash' character is commonly copied from MS Words documents and shows as – which is a Java encoding, instead of the correct URL encoding which should be â.
The expected behavior is that the Siebel application should encode all characters as URL encoding.
For example, the following steps can be performed to reproduce the problem:
1. Use a browser with "Developer Tools". In this example, we will use Firefox.
2. Navigate to any view in the application. In this case we can use the Contact List View.
3. Start "Developer Tools" and navigate to the "Network" tab of the tool.
4. Perform a query in the 'Last Name' field using:
Note the special character that looks like a normal 'Dash' character, but is actually an 'En Dash' character which is slightly longer.
5. Execute the query, and you will see that the encoding shows as Return+–+Store (the character is encoded as –), which is incorrect. This should be Return+â+Store.
Due to this issue, this can have impacts on other applications that uses the HTTP POST request.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document