The table HTTPURLLOC is used to determine the protocol, host and port when the ABAP system generates URLs - for example, to use public URLs instead of technical URLs like <host>:<port>.
In SAP_BASIS release 740 and higher, the table can be maintained with the HTTPURLLOC transaction, as explained in the SAP Note 2780619. In lower SAP_BASIS releases (up to release 731), the table can be maintained directly in the transaction SE16 - the entries should be made in upper case letters.
Fields and their meanings
Sort sequence of entries. Entries are checked in this sequence and the first matching entry is used.
Protocol for which the URL will be generated. It can be either HTTP or HTTPS.
This field can be used to filter the entry for specific applications.
Technically, the APPLICATN value depends on the "application" parameter provided by the application program, when calling the ICF method cl_http_server=>if_http_server~get_location. The value of this parameter depends on the application coding.
For generic entries, the values * (asterisk) and DEFAULT_VHOST_APPLICATIONS_DEFAULT_HOST should be used. The value * is valid for any application value, while DEFAULT_VHOST_APPLICATIONS_DEFAULT_HOST is valid when no application value is provided by the calling program.
Also, application specific entries can be maintained in this field. For example:
In addition to specific applications, it is also possible to use wildcards in this field. For example:
Note: Application specific table entries should have a lower SORT_KEY value (for example 1000) while generic or wildcard entries should have a higher SORT_KEY value (for example 9000). This is to ensure that application specific entries are checked before generic entries.
This field should be left empty, unless specified otherwise in an installation guide, best practice, etc.
|HOST||Host name to be used in the generated URL.|
Port number to be used in the generated URL.
- When testing ICF services from the transaction SICF, the table HTTPURLLOC is NOT used.
- When testing BSP applications or Web Dynpro applications from the transaction SE80, the table HTTPURLLOC is used.
- The SAP Web Dispatcher may affect the URL generation with the HTTP header x-sap-webdisp-ap. In this header the Web Dispatcher access points (ports) are specified - for example: x-sap-webdisp-ap: http=80,https=443. Depending on the value of the parameter wdisp/handle_webdisp_ap_header, these port values may override the port values specified in the HTTPURLLOC table.
SAP Note 2033765 - HTTPURLLOC entries are ignored when you test a service in SICF
SAP Note 1850486 - Enhancement to virtual host administration
SAP Note 2780619 - Maintenance view for HTTPURLLOC table