You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IPs are still not being resolved sometimes which leads to the wrong people being rate limited.
Explanation:
The API tries to resolve the client's IP but if it can't find it or it is invalid, the API assigns a null constant as the client's IP address. If some other client, who also has a null IP address now sends 60 requests in a minute, all other clients with invalid / unresolvable IP addresses also get rate limited, since the API thinks their IP addresses are the exact same.
Also on a side note: I'm talking about hashed IP addresses. Your actual IP address is not known to me at any point nor is it visible in any logs.
The text was updated successfully, but these errors were encountered:
I found out what the issue is.
It's that the resolveIP module can only resolve IPv4 addresses and can't parse IPv6.
Additionally, some headers are incorrect (use _ instead of -) and some headers don't even exist anymore.
Very very quick fix would be to use the Cloudflare header cf-pseudo-ipv4 to get an IPv4 representation of the IPv6 address and to replace the _ with -.
IPs are still not being resolved sometimes which leads to the wrong people being rate limited.
Explanation:
The API tries to resolve the client's IP but if it can't find it or it is invalid, the API assigns a null constant as the client's IP address. If some other client, who also has a null IP address now sends 60 requests in a minute, all other clients with invalid / unresolvable IP addresses also get rate limited, since the API thinks their IP addresses are the exact same.
Also on a side note: I'm talking about hashed IP addresses. Your actual IP address is not known to me at any point nor is it visible in any logs.
The text was updated successfully, but these errors were encountered: