Excessive requests #135
Comments
|
Hey Rory, Thanks for letting us know. Adding a user agent shouldn't be a problem. We are limiting the requests based on your headers as explained here. We apply this both to WS connections and HTTP requests. We don't retry HTTP failed requests. We will attempt to reconnect to WS but always respecting the rate limit. We've had a few issues with this:
We didn't receive any such reports recently. One hypothetical issue could be if the user uses both the browser and the tool extensively, in which case it might run into a rate limit (we'd have to verify this case though). That said, I'm not sure what can lead to an account restriction, it sounds like a drastic measure, that hopefully isn't applied by hitting the limit one time by accident. Could you provide more details? I've tried to reach out earlier with no success. If there's a channel for devs to ask questions (e.g. about WS limitations) or get notified about API or limitation changes it would be great to get access: |
|
If you're sure of your rate-limiting implementation then these issues are likely caused by players using older releases. This is one reason why setting a user agent is vitally important. This tool is using endpoints we don't explicitly allow or encourage so we're unable to provide support for interacting with them. Rate-limits can and will change at any time depending on our requirements of providing a stable experience to our playerbase. |
|
We're still getting requests from accounts that are hitting the rate-limit and not stopping. These requests are exceeding 1 per second and are coming from the 1.13.1 version. We recommend implementing an incremental back-off with a failure state that requires manual intervention when a connection can't be re-established. |
|
Thanks for the update. Could you show an example with request timestamps? How many users are affected? Because of network delay, requests could overlap within 1 second. As a quick improvement, I will increase that. And we will look into the incremental back-off. |
|
Sure, here's a snippet from one user: Not too many users are stuck in this state but enough to cause notable spikes in our analytics. |
|
Thanks. Hopefully v1.13.4 already helps with this, let me know. The app will auto-update upon restart so users won't get stuck on the old version for long. |
|
Looks like people are still able to get into a state where they endlessly spam requests in response to a 401 error. The tool really shouldn't attempt to make the same request again if it encounters this response code. |
|
It is important for us to automatically reconnect in case of e.g. a network outage. Didn't make a distinction between error codes so far. Provided the rate limit is respected the connection should eventually recover. When does 401 happen? Is it an invalid session id? - In that case, you're right, the connection wouldn't recover automatically. |
|
@Novynn Since yesterday we're not getting items through the websocket even though the socket is connected. Can you give any information about this? |
|
No changes have been made on our end, and data is still being streamed. |
|
This tool is still generating excessive 401 and 404 responses. If this issue isn't resolved we'll have to block it's access to our servers. |
|
@Novynn Hey Rory, we've made some improvements to the app:
With that we would like to request that you enable the client from v2.0.0 and above. |
|
That's great to hear! Do 401's and 404's also prompt the requests to stop? These are the worst offenders as mentioned:
|
|
@Novynn Thanks for the quick reply! We'll include those as well, no problem. |
|
@Novynn Hey Rory, we'll release the improved app before 3.19. It would be a web page so that it's easy to use and there's no need to install anything. In order to connect your websockets, we would need our origin whitelisted on your side, is that feasible? Thank you! |
|
The endpoint in use isn't part of our third-party offerings. I'm afraid that we aren't able to offer additional support for it at this time. |
|
Resolved in v2.0.0 |
Hello,
It's come to our attention that users of this tool are sending excessive requests to pathofexile.com resulting in their accounts being restricted. Please implement some sort of incremental back-off on failed requests (4xx's) with an automatic stop after a number of failures.
Additionally this tool should send an identifiable user-agent when making requests so that we can report these issues to you quicker without having to investigate individual cases.
Thanks,
Rory.
Grinding Gear Games.
The text was updated successfully, but these errors were encountered: