1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues


Issue #6436 resolved

Server 500 / 502 response when getting tags using the API

Erik Näslund
created an issue

I'm currently receiving a 500 or 502 response when doing a GET request to the https://api.bitbucket.org/1.0/repositories/account/repository/tags endpoint.

This has worked just fine until a few days ago when the problem started occurring. Occasionally a requests gets processed correctly, but 99% of the time it just fails.

Comments (6)

  1. Brian Nguyen

    Hi Erik,

    Are these requests timing out or are they failing with an internal server error? It is possible that the request is taking longer than 30 seconds, at that point we will kill the request and return an error.

    To verify that this is the case can you copy and paste the actual response that we return?

    Cheers, Brian

  2. Erik Näslund reporter

    Hi Brian,

    When I tried it again just now I actually got a proper response. Before I've only got a HTTP Error 502: Bad Gateway. However it took 28 seconds to receive a response for the request, which is awfully close to the 30 second timeout that you mentioned.

    We do have 877 tags in the repository I'm querying for tags, so the response we receive is 1.45MiB. Maybe we're just using the API in a way it wasn't designed for and doesn't perform well enough for?

  3. Brian Nguyen

    Hi Erik,

    That tags endpoint is definitely one of our older endpoints, so it is not as well defined as it should be. You are using it as it was intended but it just does not handle large repositories well.

    I have raised an issue #6451 to improve the scalability of the endpoint. Please watch the issue for further updates.

    Apologies for the inconvenience.

    Cheers, Brian

  4. Log in to comment