Show TOC

Process documentationProcessing HTTP Requests Locate this document in the navigation structure


The ICM processes HTTP requests and responses. On the basis of the URL and the port, a local handler in the ICM is addressed. Sharing out the requests among different handlers increases performance because a user context does not have to be created in the work process for each request. The URL prefixes used for the various handlers can be defined in profile parameters. The handlers are called in the order listed below, and they can process the request themselves or forward it to the next handler.

The SAP Web Dispatcher, which also processes HTTP requests, uses the majority of these handlers (see below).

For more information, see

Parameterization of the ICM and the ICM Server Cache

SAP Web Dispatcher


The local handlers (subhandlers) are called in the order described, provided they have been installed. Which subhandler generates the response depends on how the profile parameters for the URL prefix of the request are defined. If a subhandler has created the HTTP response, the following subhandlers are no longer included in the hierarchy. The exception is the logging handler. This carries out the HTTP logging and forwards it to the next subhandler.

  1. Logging Handler

    This handler records HTTP requests. Its use is described in Logging in the ICM.

  2. Authentication Handler

    The authorization check for the requested page is carried out here.

  3. Server Cache Handler

    This handler is used to read from and write to the ICM server cache and works as follows:

    1. Reads the request

    2. If the requested object is in the cache, it delivers the cache entry to the caller.

    3. If it isn’t (access error, cache miss), it passes the request to the next handler.

    4. Stores the entry in the cache before sending the HTTP response to the client

  4. Admin Handler

    The admin handler processes administration requests.

    For more information, see

    Processing Administration Requests

    Using the Web Administration Interface

  5. Modification Handler

    The modification handler can change the http request (header fields, URL values, and so on).

    For more information, see Modifications of HTTP Requests

  6. File Access Handler

    This handler returns a file from the file system (suitable for static files as well as images and HTML pages). The URL prefixes the static file access is to be carried out for are determined in the icm/HTTP/file_access_<xx> parameter.

    For more information, see icm/HTTP/file_access_<xx>

  7. Redirect Handler

    This handler simply forwards the HTTP request to another HTTP server (HTTP redirect). The URL prefixes the ICM is to carry out the redirect for are determined in the icm/HTTP/ redirect_<xx> parameter.

    For more information, see icm/HTTP/redirect_<xx>

  8. ABAP Handler

    This handler forwards the request to the AS ABAP and waits for a response. This is the default handler; it processes a request if no other handler is processing it. A user context is created in the work process only if this handler is being used.

    For more information, see Processing HTTP Requests in the Work Process

  9. Java Handler

    This handler forwards the request to the integrated Application Server Java.

SAP Web Dispatcher

The Web Dispatcher calls the handlers 1-7 in the same sequence, instead of handlers 8 and 9 a dispatching handler is used that balances the load and then forwards the request to the ICM of the appropriate server.