4 ms·

Isn’t this largely due to it being one of a handful of protocols that can get through typical corporate firewalls?

egberts1 3y ago
My thoughts exactly! (worth a risk of my karma for this no-so-glib remark, but ICAP protocol is busy in that HTTP examination arena) The Internet Content Adaptation Protocol (ICAP) is a lightweight HTTP-like protocol (request and response protocol), which is used to extend transparent proxy servers. This frees up resources and standardizes the way in which new features are implemented. Use cases: 1. Antivirus Scanning: ICAP allows for integration with antivirus engines. When a client requests a web resource, the proxy server can send the content to an ICAP server with an antivirus scanning module 2. Data Loss Prevention (DLP): ICAP can be used to enforce data loss prevention policies. An ICAP server with DLP capabilities can inspect outgoing web content for sensitive information, such as credit card numbers or social security numbers. 3. Content Transformation: ICAP can be used to modify web content to adapt it for specific devices or network conditions. 4. Content Filtering: ICAP can be used to implement content filtering and censorship mechanisms. By connecting a proxy server to an ICAP server equipped with content filtering capabilities, organizations can enforce policies to block or modify specific types of content, such as malware, adult content, or unauthorized websites. It is a whole new world, especially with HTTP/3 and its many variants.
- GauntletWizard 3y ago
  I hope your meaning of "glib" was "I'm describing a bunch of technologies that should not exist".
  - egberts1 3y ago
    An’it? I have designed and spun-up a new ICAP server just to deal with malicious JavaScript by certain web servers used by dubious advertising companies for protecting my home and businesses. Works better than uBlock Origin and NoJS. So, the old cat-and-mouse game is now on a briskier pace.
WorldMaker 3y ago
Not just corporate firewalls, there a lot of overly pessimistically configured by default home/consumer firewalls, routers, and ISP NAT/CGNAT gateways in the wild. "UPnP" is a hack of a solution for that in the consumer space, and it sometimes mostly works, except when it silently breaks in ways that only confuse average users and blame the application rather than their (or their ISP's) hardware.
ianburrell 3y ago
A bigger reason is all the tooling for HTTP. Every language has libraries for HTTP. There are lots of proxy servers and application servers. It works in the browser. It is all tested and reliable. Also, a lot of uses fit the request-response model of HTTP. Does it make sense to make new protocol or adapt HTTP when it can do the same thing? It makes more sense to focus on the application logic.

My thoughts exactly! (worth a risk of my karma for this no-so-glib remark, but ICAP protocol is busy in that HTTP examination arena) The Internet Content Adaptation Protocol (ICAP) is a lightweight HTTP-like protocol (request and response protocol), which is used to extend transparent proxy servers. This frees up resources and standardizes the way in which new features are implemented. Use cases: 1. Antivirus Scanning: ICAP allows for integration with antivirus engines. When a client requests a web resource, the proxy server can send the content to an ICAP server with an antivirus scanning module 2. Data Loss Prevention (DLP): ICAP can be used to enforce data loss prevention policies. An ICAP server with DLP capabilities can inspect outgoing web content for sensitive information, such as credit card numbers or social security numbers. 3. Content Transformation: ICAP can be used to modify web content to adapt it for specific devices or network conditions. 4. Content Filtering: ICAP can be used to implement content filtering and censorship mechanisms. By connecting a proxy server to an ICAP server equipped with content filtering capabilities, organizations can enforce policies to block or modify specific types of content, such as malware, adult content, or unauthorized websites. It is a whole new world, especially with HTTP/3 and its many variants.

GauntletWizard 3y ago
I hope your meaning of "glib" was "I'm describing a bunch of technologies that should not exist".
- egberts1 3y ago
  An’it? I have designed and spun-up a new ICAP server just to deal with malicious JavaScript by certain web servers used by dubious advertising companies for protecting my home and businesses. Works better than uBlock Origin and NoJS. So, the old cat-and-mouse game is now on a briskier pace.

WorldMaker 3y ago

Not just corporate firewalls, there a lot of overly pessimistically configured by default home/consumer firewalls, routers, and ISP NAT/CGNAT gateways in the wild. "UPnP" is a hack of a solution for that in the consumer space, and it sometimes mostly works, except when it silently breaks in ways that only confuse average users and blame the application rather than their (or their ISP's) hardware.

ianburrell 3y ago

A bigger reason is all the tooling for HTTP. Every language has libraries for HTTP. There are lots of proxy servers and application servers. It works in the browser. It is all tested and reliable. Also, a lot of uses fit the request-response model of HTTP. Does it make sense to make new protocol or adapt HTTP when it can do the same thing? It makes more sense to focus on the application logic.