What's the best http response for indicating this relay is gone now. 🦀 And to not make the client all hot and bother endlessly reconnecting 📡
403?
#asknostr
What's the best http response for indicating this relay is gone now. 🦀 And to not make the client all hot and bother endlessly reconnecting 📡
403?
#asknostr
Send invalid made up notes from public figures until clients notice
I've absolutely no idea and I'm sorry. I don't code. I'm an middle aged English man who can just about buy what he needs to and put it out of reach of the government. Other than that, AMA🤙🏻.
Maybe 410 Gone?
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
503 with a retry-after header
301 if its moved
404 not found for resource
410 if resource known but deleted without another address to redirect to