Make undersightable understand misconfiguration
Open
Nobody has claimed this yet.
undersightable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
<lizmat> http://design.perl6.org/ is listed as OK, but that's only at the HTTP level
<lizmat> it's misconfigured / not configured
<lizmat> perhaps checking for "nginx" in the response would be enough to catch misconfigs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the undersightable implementation and how it currently decides that an HTTP response is valid. Reproduce the check against design.perl6.org, then verify that a misconfigured response is no longer reported as OK while genuinely configured sites still pass.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100