Search Results set_response_error_check

Overview

SYS.UTL_HTTP is the Oracle-supplied PL/SQL package that provides Hypertext Transfer Protocol (HTTP) callout capability directly from SQL and PL/SQL. It is declared with AUTHID CURRENT_USER, meaning that privileges and network access are evaluated against the invoking schema rather than the package owner. Within Oracle E-Business Suite 12.1.1 and 12.2.2, the package serves as the standard integration mechanism for communicating with external web servers, REST-style endpoints, and other Internet-accessible resources over HTTP or HTTPS. It supports direct connections as well as communication through an HTTP proxy, and it permits access to other protocols (such as FTP or Gopher) via a suitably configured proxy server.

The package is classified under the ETRM API classification "OTHER" and is owned by SYS. It is referenced by eleven other packages in the E-Business Suite, confirming its role as a shared infrastructure dependency rather than an application-specific API. HTTPS calls require a properly configured Oracle wallet; non-HTTPS calls do not.

Key Procedures and Functions

The documented interface exposes 61 procedures and functions, organized into logical categories. The session API manipulates package configuration within a database user session:

• SET_PROXY / GET_PROXY — configure and retrieve the proxy server used for outbound requests.
• SET_COOKIE_SUPPORT / GET_COOKIE_SUPPORT — control and query whether HTTP cookies are maintained across requests.
• SET_FOLLOW_REDIRECT / GET_FOLLOW_REDIRECT — control and query automatic following of HTTP redirect responses.
• SET_BODY_CHARSET / GET_BODY_CHARSET — set and retrieve the character set applied to message bodies.
• SET_PERSISTENT_CONN_SUPPORT / GET_PERSISTENT_CONN_SUPPORT — manage persistent (keep-alive) connection behavior.
• SET_RESPONSE_ERROR_CHECK / GET_RESPONSE_ERROR_CHECK — control and query automatic raising of exceptions on HTTP error status codes.
• SET_DETAILED_EXCP_SUPPORT / GET_DETAILED_EXCP_SUPPORT — control and query the level of detail in raised exceptions.
• SET_WALLET — designate the Oracle wallet used for HTTPS authentication.
• SET_TRANSFER_TIMEOUT / GET_TRANSFER_TIMEOUT — configure and retrieve the timeout applied to data transfer.

The request API begins and manages outbound requests. CREATE_REQUEST_CONTEXT establishes a request context, and DESTROY_REQUEST_CONTEXT releases it. The request context is the handle through which request attributes are manipulated and information is sent to the web server. The THAT function is one of the simple, single-call functions that retrieve a web page without requiring the caller to explicitly manage the request and response sequence. Additional documented members belong to the response, cookies, and persistent connection categories, which respectively return attributes and payload data, maintain session cookies, and manage reusable connections.

Tables Accessed

No base tables or APPS-synonym tables are referenced by SYS.UTL_HTTP. All state — session configuration, cookies, request contexts, and persistent connections — is held in package memory or session-level state rather than in database tables. Consequently, the package imposes no direct data-model dependencies on the E-Business Suite schema.

Usage Notes

UTL_HTTP is typically invoked from custom PL/SQL, concurrent program logic, or application code where an outbound web service call is required — for example, retrieving a remote document, posting data to an external system, or integrating with a third-party interface. Because the package is AUTHID CURRENT_USER, the invoking schema must hold EXECUTE privilege and be granted network access through an appropriate access control list (ACL) in 11g and later databases. HTTPS calls additionally require a valid Oracle wallet configured via SET_WALLET.

The CREATE_REQUEST_CONTEXT / DESTROY_REQUEST_CONTEXT pair is central to explicit request management. A context created with CREATE_REQUEST_CONTEXT should always be released with DESTROY_REQUEST_CONTEXT once the exchange is complete, to avoid leaking session resources. The simple fetch functions (such as THAT) are preferable for one-off page retrievals, while the context-based API is appropriate when request headers, methods, payloads, or cookies must be controlled precisely. Persistent connection and cookie support settings should be reviewed when multiple calls are issued in a single session, since they change connection reuse and state retention behavior across requests.