New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some requests get a 502 Bad Gateway response #515

Closed
DuckThom opened this Issue May 2, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@DuckThom

DuckThom commented May 2, 2017

Issue found on April 28th 2017.

Endpoint(s):

  • GET /v1/me/player/currently-playing

Scope(s):

  • user-read-playback-state

Steps to reproduce:

  1. Call the endpoint

Expected behaviour:

200 Response

Actual behaviour:

Some (I'd say around 1 in a 1000) requests return a 502 Bad Gateway response:

[2017-05-02 13:32:14] production.ERROR: GuzzleHttp\Exception\ServerException: Server error: `GET https://api.spotify.com/v1/me/player/currently-playing` resulted in a `502 Bad Gateway` response:
{
  "error" : {
    "status" : 502,
    "message" : "Bad gateway."
  }
}
@arirawr

This comment has been minimized.

Show comment
Hide comment
@arirawr

arirawr May 2, 2017

Hello, we took a look into this and haven't found anything abnormal. 502 errors can occur periodically, but are not a cause for concern in these quantities. In most cases, you can re-try the request immediately and get a response.

We actively monitor errors internally and are notified of any spikes.

Thank you for your report!

arirawr commented May 2, 2017

Hello, we took a look into this and haven't found anything abnormal. 502 errors can occur periodically, but are not a cause for concern in these quantities. In most cases, you can re-try the request immediately and get a response.

We actively monitor errors internally and are notified of any spikes.

Thank you for your report!

@arirawr arirawr closed this May 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment