Issue Summary

Files are losing encoding throughout API transactions

This is reproducible on Data Center: Not tested

Steps to Reproduce

1. Upload a file with an ISO-8859-1 file encoding on it (as seen when running file --mime-encoding <filename>)
2. Fetch the API:

• https://developer.atlassian.com/cloud/bitbucket/rest/api-group-source/#api-repositories-workspace-repo-slug-src-commit-path-get

       3. Check file encoding: file -I <filename>

It returns UTF-8 encoding despite the endpoint being described as:

When path points to a file, this endpoint returns the raw contents. The response's Content-Type is derived from the filename extension (not from the contents). The file contents are not processed and no character encoding/recoding is performed and as a result no character encoding is included as part of the Content-Type.

If you clone the whole repo, the file does have the correct encoding again but if you view the response in a terminal, or write it to a file, they all always end up at UTF-8.

Expected Results

No character encoding/recoding is performed

Actual Results

Character encoding/recoding is performed

Workaround

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