Skip to content

Access phase cut off if cs disabled or no-decision #118

@rhiznomad

Description

@rhiznomad

I have multiple things happening in my access phase, cs.Allow() being one of them.
Yet when cs is disabled or there's no decision, this bouncer will call ngx.exit(ngx.DECLINED)

Doing so, nothing after cs.allow() in the access phase is processed anymore. I believe crowdsec being disabled or having no decision, should not exit the access phase completely.

Noted this issue from @blotus by searching for lua-cs-bouncer access phase and brought me in the right direction to this point; thank you for good docs. Im not aware about the satisfy any or such items and don't have a solution for that issue, yet yea; declined and thereby stopping the access phase from continuing is unfortunately not the answer either I think.

Edit: ngx.declined is also set for enable_internal and exclude_location (whitelist) related use cases.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions