Maybe 410 Gone?
Discussion
Ya what do major clients like coracle do with a 403ish?
Whatever the default is, I don't actually know if the status code is even available on the websocket object. It's just treated as a failure in Coracle.
Cc nostr:npub1yx6pjypd4r7qh2gysjhvjd9l2km6hnm4amdnjyjw3467fy05rf0qfp7kza well, 403 isn't working so well so I might as well try 410 😎
Ya 410 isn't natively supported by haproxy, but the cool thing is haproxy serves the 403 error pages directly from ram so ... Trying 410 may be fruitless for now, tho I know how to deploy it I doubt clients will treat it any different than a catch-all retry