Closed mhamzahkhan closed 1 year ago
Conclusion: Treat same as spam request, prefer to block request with reverse-proxy or skip logging about that with your logging solution. ( by User-Agent, IP Address, and so on...)
Principle: Point 1: Using Activity-Relay ( send activity to /index ) are limited for subscriber only. Point 2: Activity-Relay acts returning 400 for unallowed requests. ( 401 might be better? But that's not the point. ) Point 3: By unclear reason mastodon.social sent delete request for your relay without subscription. ( Maybe when account deletion it will send delete to all peers...? But I don't know details... )
Hello,
I've noticed there has been an increase in HTTP 400 responses lately from my relay. It appears to be when a user gets deleted on a subscribed instance. Is there any way to perhaps suppress this?
Eg this message from mastodon.social:
and the response: