The branch list page shows build summary information for each branch (if build summary information exists for that branch). When scrolling down the branch list page, eventually requests to retrieve build summaries will start failing.
- Create a repository with a significant number of branches (e.g. 1000+ branches)
- Visit the branch list page with developer tools open and scroll down
All requests for build summaries are successful.
After scrolling down far enough, the requests for build-summaries will start failing with the following response:
This can be seen in e.g. browser development tools, but is not logged in the Bitbucket logs.
Build summaries will not be loaded for any branches beyond where the failed requests started.
- Instead of scrolling down and paging, if only specific branches are of internet, the filter can be used to restrict the number of branches shown in the table.
- The server.max-http-header-size application can be used to increase the limit of the total size of HTTP headers for a single request.