Skip to content

Domain input should handle URLs with paths or schemes #43

@pparage

Description

@pparage

Describe the Bug
On the web test page (homepage), entering a domain that includes anything other than a plain domain like example.com—for example, using wildcards or including a scheme like https://—results in an error. It seems the input is not properly sanitized or escaped, and there may be missing logic to handle URLs with schemes or paths.

To Reproduce
Steps to reproduce the behavior:

Expected Behavior
The test should handle domains entered with protocols (like https://) or paths gracefully by either:

  • Stripping unnecessary parts (e.g., path or scheme), or

  • Properly escaping and interpreting them to ensure the test can still run.

Suggested Fix

  • Validate and normalize input by extracting only the relevant domain part.

  • Add a frontend warning or automatic correction when incorrect formats are entered.

  • Consider supporting full URLs as input if technically viable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions