Cannot download LFS binary data via API; just downloads the pointer file.
Steps to reproduce
Curling against an internal/private repo, you used to be able to target the file directly, like this:
However, that's no longer allowed, and was deemed a security concern, so we have to go through the API, like this:
If it's an LFS file, you get the pointer:
version https://git-lfs.github.com/spec/v1 oid sha256:0678174690c9368bb7dae01edc612897cee0850a95f106bb756128afdc0b4886 size 9845
What is the current bug behavior?
Currently, you get the LFS pointer. Arguably, this is fine even though I would argue that 99% of use cases want the binary. There is no way to pull binary.
What is the expected correct behavior?
Pull the binary via the raw endpoint. Alternatively create an LFS endpoint that pulls the binary data.
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com