Problem Definition

When accessing raw git lfs files via its URL, caching headers and other caching data is not provided which means that repeatedly access data is not cached. Given the structure of git lfs objects and URL’s, the likelihood of the content changing would be low, therefore, making caching for lfs content a good candidate.

Suggested Solution

Provide support for caching headers and other caching data such as content-length.

Why Suggestion Is Needed 

Providing support for caching headers and other caching data such as content-length would provide the size of the lfs object on retrieval through its raw URL and allow the generation of a download progress bar. Additionally, repeatedly accessed lfs objects could be cached by processes such as build servers for builds.