Transports and Interfaces: Siebel Enterprise Application Integration > EAI HTTP Transport >

Using POST and GET

The HTTP protocol supports the GET and POST methods. You might be familiar with these methods if you have ever built a Web-based CGI form:

  • GET. Requests a representation of the specified resource. GET is the most common method used on the Web today.
  • POST. Submits data to be processed, such as from an HTML form, to the identified resource. The data is included in the body of the request. This might result in the creation of a new resource, updates to existing resources, or both.

The EAI HTTP Transport imposes certain restrictions on your use of transport features when using POST or GET method. Table 18 identifies restrictions on these HTTP methods.

Table 18. Restrictions on GET and POST Methods with EAI HTTP Transport


The HTTP Body has no significance when using GET. During a GET process, only the universal resource locator (URL) is used for the request.


The HTTP Body is relevant only when using POST. The HTTP Body is encoded with a default mechanism used to encode URLs.The HTTP Content-Type application/xxx-form-urlencoded is the default content type used for request bodies. The content is sent as it is without any special content encoding, such as Base64.

Transports and Interfaces: Siebel Enterprise Application Integration Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.