Cc nostr:npub1yx6pjypd4r7qh2gysjhvjd9l2km6hnm4amdnjyjw3467fy05rf0qfp7kza well, 403 isn't working so well so I might as well try 410 😎
Discussion
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