Skip to content

Incorrect Content-type returned #79

Answered by shevron
ghost asked this question in Q&A
Discussion options

You must be logged in to vote

What storage backend are you using (assuming local / streaming based on the info)? Not all backends support properly sending content-type headers.

To give some background, Content-type is not somethnig handled by the Git LFS protocol (typically this isn't needed by Git LFS). Some of the storage backends supported by Giftless have extra functionality to handle content-type headers, but local storage doesn't store information about the content type anywhere, and so adding support for it can be done but might require some guessing or extension of the protocol. This was briefly discussed here: #68 but nothing was done to handle content-type, just content-disposition header.

In any case if you…

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@ghost
Comment options

Answer selected by shevron
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant