The available settings to be configured regarding the profile are There are 2 sections where ICAP is configured: Servers When configuring ICAP on the FortiGate unit, you must configure an ICAP profile that contains the ICAP server information this profile is then applied to a security policy. If the FortiGate unit supports HTTPS inspection, HTTPS traffic intercepted by a policy that includes an ICAP profile is also offloaded to the ICAP server in the same way as HTTP traffic. You can offload HTTP responses or HTTP requests (or both) to the same or different ICAP servers. Responses from the ICAP server are returned to the FortiGate unit which forwards them to an HTTP client or server. If you enable ICAP in a security policy, HTTP traffic intercepted by the policy is transferred to an ICAP server in the ICAP profile added to the policy. For instance ICAP messages can not be forwarded by HTTP surrogates. To HTTP/1.1 it is not HTTP nor does it run over HTTP, as such it cannot be treated as if it were HTTP. While ICAP is a request/response protocol similar in semantics and usage The messages going back and forth between the client and server are typically HTTP requests or HTTP responses. Once the ICAP server has finished processing the the content, the modified content is sent back to the client. Content Adaptation refers to performing the particular value added service, or content manipulation, for an associated client request/response.Įssentially it allows an ICAP client, in this case the FortiGate firewall, to pass HTTP messages to an ICAP server like a remote procedure call for the purposes of some sort of transformation or other processing adaptation. ICAP is usually used to implement virus scanning and content filters in transparent HTTP proxy caches. Its purpose is to support HTTP content adaptation by providing simple object-based content vectoring for HTTP services. The default TCP that is assigned to it is 1344. It is an Application layer protocol and its specifications are set out in RFC 3507. The protocol is a lightweight member of the TCP/IP suite of protocols.
ICAP servers are focused on a specific function, for example: Off-loading value-added services from Web servers to ICAP servers allows those same web servers to be scaled according to raw HTTP throughput versus having to handle these extra tasks. This takes some of the resource strain off of the FortiGate firewall leaving it to concentrate its resources on things that only it can do. ICAP is the acronym for Internet Content Adaptation Protocol The purpose of the feature is to off load work that would normally take place on the firewall to a separate server specifically set up for the specialized processing of the incoming traffic.
0 kommentar(er)
