Large page size parameter in content REST API causes performance degradation

Issue Summary

The Bitbucket get file content REST API currently does not have a maximum limit imposed on the page size (limit parameter) for paged requests. This can lead to performance degradation when consumers specify a large limit, resulting in longer response times and increased load on the system. To enhance user experience and maintain system stability, we will need to impose a maximum limit for the page size.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Send a request to the Bitbucket get file content REST API with a paged request (start, limit).
2. Choose a relatively large file (eg. over 1GB in size)
3. Specify a large number for the limit parameter (eg. 200000).
4. Observe the response time and system load.

Expected Results

The response time should be reasonable, and the system load should not be significantly impacted by the limit parameter.

Actual Results

When specifying a large limit parameter, the response time is longer and the system load is increased, potentially leading to system overload and degraded performance for users.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.