Replying to Avatar fiatjaf

How about we use WebSocket status code 4000 for when the relay wants to close the connection and doesn't want the client to try to connect again -- for example, because it requires payment and the client is not a paying user?
Avatar
Mike Dilger ☑️ 2y ago

I like the idea. Gossip would honor it until restart, most probably. HTTP 402 (payment required) and 403 (forbidden) also seem reasonable.

Reply to this note

Please Login to reply.

Discussion

Avatar
Mike Dilger ☑️ 2y ago

Looking at my code it wasn't handling HTTP status codes from the relay at all. So I made changes. Now, on many serious errors including unauthorized, forbidden, not found, payment required, etc, gossip doesn't retry.