SES ApplicationContainer Is Unable To Encode Space Present In The Outbound URL
(Doc ID 2751825.1)
Last updated on APRIL 04, 2025
Applies to:
Siebel CRM - Version 20.9 and laterInformation in this document applies to any platform.
Symptoms
While triggering request to external system through EAI HTTP Transport/Outbound web service, request will go through SES applicationcontainer i.e ContainerURL mentioned in the JAVA64 profile.
In 20.5 , sample URL is
HTTPRequestURLTemplate = http://localhost:9012/siebel/outboundeai?eaioutboundurl=https://<AIHOST.example.com>:<AI_HTTPS_Port>/siebel/v1.0/data/Service Request/Service Request/1-1234
and its working fine.
But in 20.9 , same URL is converted to
Request URL = http://localhost:9012/siebel/outboundeai?eaioutboundurl=https://<AIHOST.example.com>:<AI_HTTPS_Port>/siebel/v1.0/data/Service%20Request/Service%20Request/1-234
spaces were replaced by %20 and in catalina.log file , the below errors were found.
Cause
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
Symptoms |
Cause |
Solution |
References |