ICAP integration

Airlock Microgateway supports the Internet Content Adaptation Protocol (ICAP) to hand off HTTP messages to an external ICAP server for inspection and adaptation. ICAP is defined in RFC 3507.

Scope and supported mode

Airlock Microgateway currently supports ICAP in REQMOD mode (request modification). It does not support RESPMOD mode (response modification).

Further limitations (current implementation)

Typical use case

The primary use case for ICAP is antivirus/malware scanning of incoming requests before they reach backend services.

Extensibility use case

If you implement your own ICAP server, you can use ICAP to capture, analyze, and modify HTTP requests. This allows you to extend Airlock Microgateway with custom adaptation logic (e.g., content checks, metadata enrichment, header/body rewrites, or request blocking), using an approach similar to the ICAP integration described for Airlock Gateway.

Configuration reference

Configuration details are documented in the API Reference under 𝙸𝙲𝙰𝙿𝙿𝚘𝚕𝚒𝚌𝚢 and 𝙸𝙲𝙰𝙿𝙿𝚛𝚘𝚟𝚒𝚍𝚎𝚛.