Information for RPM libecap-1.0.1-2.module+el8.8.0+674+0993c1fc.src.rpm
| ID | 407114 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Build | libecap-1.0.1-2.module+el8.8.0+674+0993c1fc | ||||||||||
| Name | libecap | ||||||||||
| Version | 1.0.1 | ||||||||||
| Release | 2.module+el8.8.0+674+0993c1fc | ||||||||||
| Epoch | |||||||||||
| Arch | src | ||||||||||
| Draft | False | ||||||||||
| 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. | ||||||||||
| Build Time | 2023-06-05 13:23:19 GMT | ||||||||||
| Size | 343.67 KB | ||||||||||
| 8a48a64872af64b89dd98975ab96577a | |||||||||||
| License | BSD | ||||||||||
| Buildroot | module-squid-4-8080020230605115757-fd72936b-build-100505-51240 | ||||||||||
| Provides | No Provides | ||||||||||
| Obsoletes | No Obsoletes | ||||||||||
| Conflicts | No Conflicts | ||||||||||
| Requires |
|
||||||||||
| Recommends | No Recommends | ||||||||||
| Suggests | No Suggests | ||||||||||
| Supplements | No Supplements | ||||||||||
| Enhances | No Enhances | ||||||||||
| Files |
|
||||||||||
| Component of | No Buildroots | ||||||||||
