Files
OpsLog/internal/extsvc
rouggy 1ac00c101e fix(clublog): say what is wrong, not four kilobytes of markup
Club Log refuses with its ordinary web page rather than an error string, so the
new test reported a rejected login by pasting a 403 page — title, stylesheets,
navigation and all — into the status bar. The body now goes to the log, where a
real diagnosis happens, and the operator gets the one sentence there is to act
on: check the e-mail, the password and the logbook callsign.

Dropped the startyear=2099 filter with it, and that one matters more than it
looks. It was there to keep the reply small, but it was never verified against
Club Log's API — and Club Log answers an unrecognised request with the SAME 403
it uses for a refused login. An unverified parameter would therefore have made
every CORRECT password look wrong, which is precisely the failure this change
set out to end. The reply is capped at 4 KB and closed at once instead; the
status code arrives ahead of the body either way.
2026-08-11 15:34:06 +02:00
..
2026-07-27 00:16:17 +02:00
2026-07-09 17:32:13 +02:00
2026-06-18 22:58:00 +02:00
2026-07-27 00:16:17 +02:00
2026-07-02 11:41:53 +02:00