Skip to content

message parsing is too strict #602

@slingamn

Description

@slingamn

modern says that "These message parts, and parameters themselves, are separated by one or more ASCII SPACE characters (' ', 0x20)."

The current ircmsg.Parse implementation treats two consecutive spaces between parameters as an attempt to send an empty parameter as a non-trailing, and errors out; the user gets disconnected with Received malformed line. This is probably wrong.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions