Skip to content

Ways to control the log level when an attack is detected #3

@agentzh

Description

@agentzh

Currently this module directly prints an error log level messages to nginx's error.log file, which itself can be one kind of DoS attack because error log messages are always non-buffered and thus quite expensive. It'd be nice if you can provide a config directive to control the log level by the user.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions