My Oracle Support Banner

Should Special Characters Be URL Encoded While Using GET And POST Methods Of EAI HTTP Transport (Doc ID 975854.1)

Last updated on FEBRUARY 05, 2019

Applies to:

Siebel CRM - Version 7.0.4 SIS [14068] and later
Information in this document applies to any platform.

Purpose

URL encoding (also know as Percent-encoding), is a mechanism for encoding reserved characters.

Reserved characters are those characters that sometimes have special meaning (referred to as special characters in this document). 

Examples of reserved/special characters include & , ! , “ , ‘ , : , # , : , % etc. Unreserved characters have no such meaning. Using URL encoding, characters which otherwise would not be allowed are represented using allowed characters.

This document explains the necessity of URL encoding for data received by way of Siebel Inbound HTTP.

Scope

Applies to all data handling involving special characters and Non ASCII characters received over Siebel Inbound HTTP.

Details

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
Purpose
Scope
Details
 1. For HTTP GET data is sent as a part of URL, so special characters should always be URL encoded.
 2. POST requests can send the data without URL encoding.
References

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