Skip to content

UI: better error messaging when invalid protocol is requested? #772

@SgtPooki

Description

@SgtPooki

see #759 (comment)

Basically, if you access https://inbrowser.dev/potato/QmWhatever/foo, or other invalid protocol in the path, it loads the landing page, which could be confusing.

Loading a subdomain shows "page not found" on inbrowser.dev: https://qmwhatever.potato.inbrowser.dev/

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Medium: Good to have, but can wait until someone steps upeffort/hoursEstimated to take one or several hoursenhancementNew feature or requestexp/beginnerCan be confidently tackled by newcomerskind/enhancementA net-new feature or improvement to an existing featureneed/analysisNeeds further analysis before proceedingneed/maintainers-inputNeeds input from the current maintainer(s)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions