Skip to content

Implement Memcache support as Collection backend on libmodsecurity #1140

Closed

Description

@zimmerle

ModSecurity version 3 architecture allow the utilization of multiple backends, including memcache. The support should be implemented. The interface is available here:

https://github.com/SpiderLabs/ModSecurity/blob/libmodsecurity/headers/modsecurity/collection/collection.h

Activity

  1. self-assigned this
    on May 5, 2016
  2. theadoria commented on Aug 18, 2016

    @theadoria

    Will this support connecting to memcache over a unix socket? Would be very useful for multi tenant environments :)

  3. zimmerle commented on Aug 25, 2016

    @zimmerle
    ContributorAuthor

    Hi @tedwardia, please check #1139

  4. modified the milestones: v3.0.1, on Apr 2, 2018
  5. modified the milestones: v3.0.3, v3.0.4 on Sep 5, 2018
  6. fzipi commented on Oct 12, 2026

    @fzipi
    Collaborator

    Revisiting this one. Same topic as #1139, which already points here and has the discussion. Let's close this one in favour of #1139.

  7. added
    duplicateOps. Somebody else already hit that bump
    needs decisionTriage done; a maintainer needs to make the final call
    on Oct 12, 2026
  8. airween commented on Oct 12, 2026

    @airween
    Member

    Indeed we should close this one.

    A side note: I started to work on v4 where the first big change is that the admin can configure the backend. Actually, there is only one "external" backend (which is persistent), the LMDB. In my local repository now I can set up the path to LMDB file.

    This will fix the issues like #3394.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions