Skip to content

[gui] Trigger 404 within protocol route when protocol is not ws or wss #776

Description

@dskvr

Presently, the route will still load, and it is rather confusing. Instead, trigger a 404

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions