[ol8_appstream] libecap-1.0.1-2.module+el8.3.0+7819+eb7d4ef6.x86_64

Name:libecap
Version:1.0.1
Release:2.module+el8.3.0+7819+eb7d4ef6
Architecture:x86_64
Module:squid:4:8030020200828070549:9edba152
squid:4:8040020201207074920:9f9e2e7e
squid:4:8040020210420090912:522a0ee4
squid:4:8050020210618131503:b4937e53
squid:4:8060020220209171548:d63f516d
squid:4:8060020220628135610:ad008a3a
squid:4:8060020220928033422:ad008a3a
squid:4:8080020221208121636:fd72936b
Group:Development/Libraries
Size:52525
License:BSD
RPM: libecap-1.0.1-2.module+el8.3.0+7819+eb7d4ef6.x86_64.rpm
Source RPM: libecap-1.0.1-2.module+el8.3.0+7819+eb7d4ef6.src.rpm
Build Date:Wed Nov 04 2020
Build Host:jenkins-172-17-0-2-c7d4fba2-72eb-41b9-9372-029207b11421
Vendor:Oracle America
URL:http://www.e-cap.org/
Summary:Squid interface for embedded adaptation modules
Description:
eCAP is a software interface that allows a network application, such as an
HTTP proxy or an ICAP server, to outsource content analysis and adaptation to
a loadable module. For each applicable protocol message being processed, an
eCAP-enabled host application supplies the message details to the adaptation
module and gets back an adapted message, a "not interested" response, or a
"block this message now!" instruction. These exchanges often include message
bodies.

The adaptation module can also exchange meta-information with the host
application to supply additional details such as configuration options, a
reason behind the decision to ignore a message, or a detected virus name.

If you are familiar with the ICAP protocol (RFC 3507), then you may think of
eCAP as an "embedded ICAP", where network interactions with an ICAP server are
replaced with function calls to an adaptation module.

Changelog (Show File list) (Show related packages)