938df5c47f
For the majority of Git LFS's lifetime, Git LFS objects have been uploaded via HTTP and contained the header: Content-Type: application/octet-stream In [1], this changed and we began attempting to guess an appropriate Content-Type header based on the first 512 bytes of the file being uploaded. This breaks some hosting platforms' implementation of this API, so let's offer a way to disable this guessing to allow users to upload objects again on affected implementations. [1]: a1736293 (Merge pull request #3137 from calavera/set_upload_content_type, 2018-07-23) |
||
---|---|---|
.. | ||
schemas | ||
adapterbase.go | ||
api_test.go | ||
api.go | ||
basic_download.go | ||
basic_upload.go | ||
custom_test.go | ||
custom.go | ||
errors_test.go | ||
errors.go | ||
manifest_test.go | ||
manifest.go | ||
meter.go | ||
transfer_queue_test.go | ||
transfer_queue.go | ||
transfer_test.go | ||
transfer.go | ||
tus_upload.go | ||
verify_test.go | ||
verify.go |