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


Issue #8867 closed

GET /xhr/source-lastmod/* request throws "500: Something went wrong" (BB-10030)

Paul Kilgo
created an issue

I uploaded a pretty big git repository (OK it's git's own repository) and noticed that the commit messages weren't showing up in the directory listing. I used my browser's network profiler and noticed it was failing on this URL:


When visiting the page, it gave me a code:


Comments (2)

  1. Brian Nguyen

    Hi Paul,

    The last modified endpoint is failing because it exceeds Bitbucket's 30 second threshold for serving requests.

    The repository is actually not that large, but the slowness of the endpoint is actually determined by the age of the oldest commit in the directory. For example, if there is a file that hasn't been updated since commit #1, Bitbucket needs to traverse the entire commit history to find it.

    Nevertheless, we continue to look for ways to improve the performance of our site, and so I've added this to our backlog so that we can monitor this in the future.

    Cheers, Brian

  2. Log in to comment