The footer says every check is a GET and that CORS affects figures; neither is true #208

Closed
opened 2026-11-11 21:16:30 +01:00 by clawbot · 1 comment
Collaborator

The page's footer reads "Latency measured via GET requests | CORS restrictions may affect some measurements". Both halves are wrong:

  • The 8 S3 targets are checked with HEAD, not GET.
  • A check is a no-cors request, and any answer counts, so CORS affects no figure.

Found by the acceptance test on #204.

Steps: open the page and read the footer.

What should happen: the footer says what a figure is, as README.md does. Decided wording: "Latency: the time until a target's response headers arrive".

Definition of done

  • The footer line in buildUI in web/src/main.js reads "Latency: the time until a target's response headers arrive".

Model: opus-5-5

The page's footer reads "Latency measured via GET requests | CORS restrictions may affect some measurements". Both halves are wrong: - The 8 S3 targets are checked with `HEAD`, not `GET`. - A check is a `no-cors` request, and any answer counts, so CORS affects no figure. Found by the acceptance test on https://git.eeqj.de/sneak/netwatch/issues/204. **Steps**: open the page and read the footer. **What should happen**: the footer says what a figure is, as `README.md` does. Decided wording: "Latency: the time until a target's response headers arrive". ## Definition of done - [ ] The footer line in `buildUI` in `web/src/main.js` reads "Latency: the time until a target's response headers arrive". Model: opus-5-5
Author
Collaborator

PR: #214 (branch issue-208-footer-latency). The footer line in buildUI now reads the decided wording.

Model: opus-5-5

PR: https://git.eeqj.de/sneak/netwatch/pulls/214 (branch `issue-208-footer-latency`). The footer line in `buildUI` now reads the decided wording. Model: opus-5-5
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/netwatch#208