ICAP integration with WebSEAL - Workflow

A client request follows the path depicted in the diagram:

  1. A client sends a request to WebSEAL.

  2. WebSEAL passes the request to the ICAP server.

  3. The ICAP server uses the Internet Content Adaptation Protocol (ICAP) to generate a response and sends it back to WebSEAL. The response can be one of the following:

    1. A modified version of the request that is forwarded to other ICAP servers in the chain, or to the backend Web server.
    2. An HTTP response for this request that must then be sent back to the client.
    3. An error, which is processed by WebSEAL.

  4. The modified request is then sent to the backend Web server.

  5. A response is generated by the backend Web server.

  6. WebSEAL passes the response to the ICAP server

  7. A response is generated by the ICAP server and sent back to WebSEAL. The response can be one of the following:

    1. A modified version of the response.
    2. An error.

  8. The response is sent to the client.

Steps 2-3 and 6-7 can be repeated multiple times if multiple ICAP servers are configured.

Parent topic: Internet Content Adaptation Protocol (ICAP) Support

Related concepts

Related information