2578665 - How to maintain the table HTTP_WHITELIST

• It is unclear which entries should be maintained in the table HTTP_WHITELIST.
   
• Runtime errors (short dumps) of type UNCAUGHT_EXCEPTION / CX_HTTP_WHITELIST occur. The "Error analysis" section of the dump contains an error message, similar to the ones below:
  URL Parameter <Unknown> does not exist in HTTP whitelist 
  URL parameter sap-theme does not exist in HTTP whitelist 
   
• When trying to access browser-based applications (e.g. WebGUI, Web Dynpro, BSP, Fiori etc.), an HTTP 500 error is displayed with the message "URL Parameter <Unknown> does not exist in HTTP whitelist (termination: RABAX_STATE)" or "URL parameter sap-theme does not exist in HTTP whitelist (termination: RABAX_STATE)".
  
  
• When trying to access browser-based applications embedded in an Enterprise Portal page, the following is displayed in a javascript alert popup: "The whitelist service cannot be reached. Status: 403".

• Note - there are two solutions for HTTP whitelisting. Read the SAP Note 2667053 for details.
  1. The older solution is using the database table HTTP_WHITELIST - this is what the current KBA describes.
  2. The more recent solution is the UCON Allowlist, delivered with the SAP Note 2573569. This KBA is not relevant for the UCON Allowlist. For the UCON solution, read KBA 3290787 - How to maintain entries in transaction UCON_CHW?
  
  Both solutions provide a similar functionality, and only one of these is active in any NW ABAP system at any time. The above symptoms may be caused either by an incorrectly/incompletely maintained HTTP_WHITELIST table, or an incorrectly/incompletely maintained UCON Allowlist, depending on which one is active in the system. 
  If unsure which whitelist/allowlist is used, call the transaction UCON_CHW and check the system response:
  a. If a welcome popup is displayed or the transaction does not exist, then the classic HTTP_WHITELIST is used.
  b. If the transaction is displayed without a welcome popup, then the UCON Allowlist is used.

• SAP NetWeaver
• SAP Web Application Server for SAP S/4HANA
• ABAP Platform

UNCAUGHT_EXCEPTION, CX_HTTP_WHITELIST, HTTP_WHITELIST, URL Parameter <Unknown> does not exist in HTTP whitelist, URL parameter sap-theme does not exist in HTTP whitelist, Web Dynpro ABAP permission denied, No validation message from parent received, whitelist, whitelistservice, allowlist, allowed, embedded, /sap/public/bc/uics/whitelist/service, slash, missing, The whitelist service cannot be reached. Status: 403, UCONCOCKPIT, UCON, Unified Connectivity, 500 Internal Server Error , KBA , url parameter does not exist , in http white list , url parameter sap-theme does not exist , does not exist in http white list , whitelist , BC-MID-ICF , Internet Communication Framework , BC-FES-ITS , SAP Internet Transaction Server , BC-WD-ABA , Web Dynpro ABAP , BC-CST , Client/Server Technology , BC-FES-BUS-HTM , HTML , BC-BSP , Business Server Pages , CA-FLP-FE-COR , SAP Fiori Launchpad Frontend Core and Services , BC-FES-BUS-RUN , Runtime , Problem