SAP Knowledge Base Article - Preview

2542038 - URL Generation in SAP Gateway (OData) responses not works as expected

Symptom

URLs (absolute URLs in ATOM IDs, media links, XML base URLs) in the generated OData response are pointing to other protocol, host or port then required (for example: internal host instead of external/public host; http instead of https; wrong port).

Location of these URLs in the metadata document, service document or the response for any other request can be:

  • In the HTTP Response header:
    • location
    • etc.
  • In the HTTP Response body:
    • metadata -> id
    • deferred -> uri
    • app:service -> xml:base
    • atom:link -> href
    • media_src
    • etc.

    Read more...

    Environment

    • SAP Gateway
    • SAP NetWeaver

    Product

    SAP Gateway all versions ; SAP NetWeaver all versions

    Keywords

    HTTPURLLOC, Web Dispatcher, reverse proxy, url, https, http, ATOM IDs, load balancer, absolute URL, media links, XML, media_src, /IWCOR/CL_DS_HDLR_HTTP, /IWCOR/IF_REST_APPLICATION~GET_ROOT_HANDLER, CL_HTTP_SERVER, get_location_exception, applicatn , KBA , icf , sicf , OPU-GW-COR , Gateway Framework , BC-CST-IC , Internet Communication Manager , BC-MID-ICF , Internet Communication Framework , BC-CST-WDP , Web Dispatcher , OPU-FND-CCL , Gateway Consumer Connectivity Layer , Problem

    About this page

    This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

    Search for additional results

    Visit SAP Support Portal's SAP Notes and KBA Search.