> HTTP 200 OK
> look inside
> actually 401 Unauthorized wrapped in JSON for some reason
@whitequark I have a very faint memory of that being a thing around 15y ago and it had to do either with some browsers either not accepting empty body replies with 202s (and maybe 200s) or some ajax bs with some bigger framework and so it was actually not too uncommon. Unless this is some ancient unmaintained stuff (and my memory not completely failing) it's probably just normal jank or incompetence though.