Skip to content

[BUG] CAPABILITY accepts invalid arguments #260

Description

@Aravinda-HWK

Steps to Reproduce

Current command dispatch always routes CAPABILITY to the handler without argument validation.

Expected Behavior

RFC 3501 says CAPABILITY takes no arguments and invalid arguments should result in BAD.

Actual Behavior

The current handler does not check the argument count and always returns CAPABILITY plus tagged OK.

Relevant Logs / Screenshots

Result: a client sending something like A1 CAPABILITY EXTRA would likely get OK instead of BAD.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood first issueGood for newcomers

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions