Skip to Main Content
Feature Request FR-4979
Product Area APIs
Status CLOSED

1 Voters

apex_web_service should use utl_http.create_request_context

weberge42 Public · Aug 5 2026

Idea Summary
apex_web_service should use utl_http.create_request_context or accept an UTL_HTTP.REQUEST_CONTEXT_KEY

Use Case
To overcome the problem with mixed usage of p_wallet_path = <some_path" and p_wallet_path="system:" in the same database session.

Preferred Solution (Optional)
use utl_http.create_request_context for every request or accept an parameter of type  UTL_HTTP.REQUEST_CONTEXT_KEY

Should be an easy change - 2 calls to utl_http

system: is available since 19.16 and documented in the 19c docs, e.g. "Table 273-58 SET_WALLET Procedure Parameters" or "Table 273-22 CREATE_REQUEST_CONTEXT Function Parameters"

please see also SR 4-0003427811 and SPIN-OFF SR 4-0003377347

We reviewed this idea carefully, and while it was interesting, we concluded that it is unlikely to make its way into APEX in the foreseeable future.

Comments

Comments

  • carsten.czarski APEX Team OP 5 days ago

    Should be an easy change - 2 calls to utl_http

    There is of course more to this. APEX_WEB_SERVICE is part of APEX since APEX 3.0 - we have several thousands of applications using the package in several different ways. Even if it looks simple, this requires significant testing effort.

    As I commented on FR-4347: The goal of this is actually working around a database issue on some 19c versions. Also, one can always continue using a database wallet instead of relying on SYSTEM:. And there is the option of upgrading to 26ai database.

    With all that in mind, and all the other ideas being raised on this forum, I see it unlikely for us to prioritize this one.