@artemist the only websockets I’ve ever handled preferred status codes in the 1000 region. To be fair it was only once I actually did websocket stuff and it was for one specific api. I say once but I had to maintain it and deal with their stupid little status codes. Drove me up the wall resuming etc. I don’t doubt you though just haven’t seen it myself.
@easrng yea I noticed that just now. Well glad I don’t work in websocket space anymore. I’d rather deal with udp or tcp sockets, websockets are kinda bleh.
@k I don’t see 402 in the wild because people just don’t use it, they hide paid access behind authorized access so you’ll see 400, 401, 403 but never someone outright giving 402. I’ve never seen that in the wild.
Add comment