HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Add a new idea Subscribe
Status Needs Review
Workspace Domino
Categories Administration
Created by Guest
Created on May 30, 2022

RELATED IDEAS

Make HTTP return codes from ICAP configurable

Domino 12.0.2 introduces ICAP. While it has been tested with TrendMicro and McAfee only at the moment, there are other AV solutions available that could be used with this new feature.
While evaluation ClamAV with c-icap, I found that The return codes from c-icap cause an error in MailScan.

The problem is that c-icap returns i.e "HTTP/1.0 403 Forbidden". That is the expected code that will be returned when a virus has been found. There seems nothing wrong at first sight.

BUT: MailScan runs into an error because it expects "HTTP/1.1 403 Forbidden". Spot the difference?


It would make sense to make this configurable in the MailScan configuration. The same applies for other return codes. ( 200, 204, 206 ... )

Leave it at HTTP/1.1 as the default, but let us override the protocol/version if needed.

  • Attach files
  • Guest
    Reply
    |     Dec 11, 2024

    CSCAN_ICAP_VIRUS_RETURN_CODES=201
    https://ds_infolib.hcltechsw.com/ldd/fixlist.nsf/738a582afa78208a852570c900548069/29d1b92cee16293e852589f60070b904?OpenDocument

  • Guest
    Reply
    |     Oct 7, 2023

    the c-icap project isn't a well supported project, which should be used in production. it is good for POC environments, but I would not base and production anti-virus scanning on it.
    the fact that they still use HTTP 1.0 alone shows that the project is not well maintained.

    c-icap is usually a bridge to use ClamAV. it would make much more sense to support the ClamAV protocol native.

    there is an AHA idea for ClamAV support.


Copyright © 2023 HCL Technologies Limited