My Oracle Support Banner

Addresses Dual URL Encoding On Outbound REST Requests that Include Path Parameters (Doc ID 2878448.1)

Last updated on JULY 21, 2022

Applies to:

Siebel Public Sector Service - Version 20.10 and later
Information in this document applies to any platform.


REST Outbound: url-encoded path parameters are being re-encoded by Siebel.


1. Follow the steps mentioned in doc How To Set Up And Test Outbound RESTFul API Services From 20.8 onwards (Doc ID 2739175.2) to configure Outbound Rest API.
2. Import attached JSON file account_mod.json as mentioned in tab Creating Proxy Objects By Importing JSON file.
3. Simulate the BS by following the steps mentioned in III. Testing the Outbound RESTFul API Call.
4. Please ensure to pass a valid Account Row_id to the Input Argument account_key:path and see if it is working properly.
5. Now pass a Row_Id like 1-GOUL%2F12 which is the encoded form of 1-GOUL/12. That is we are replacing the '/' with '%2F'.
6. Now trigger the request.
7. Request will fail as the Row_Id is not present.
8. Now check the logs localhost_access_log and RESTInBoundDefault.log in the folder root\ai\applicationcontainer_external\logs for the Row_Id in the URL.



9. The Row_Id gets re-encoded with '%252F'


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.