Description
When browsing LFS files in the Web UI, if the file is not an image that can be rendered, a download link is presented. When a file is downloaded via this link, in Bitbucket Server 5.9.0 the file name is just the LFS object id (the SHA256 hash), where it should be the real filename.
The file name is actually set by having the browser sent a URL parameter "response-content-disposition", then the server in its response use this filename in its Content-Disposition header. As of 5.9.0 it appears the front end is double encoding the URL, and as a result breaking this functionality.
Here is an example URL: