mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[PR #1137] [MERGED] use correct content-type when overwriting and copying files #1846
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#1846
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/1137
Author: @liuyongqing
Created: 8/26/2019
Status: ✅ Merged
Merged: 8/29/2019
Merged by: @gaul
Base:
master← Head:master📝 Commits (3)
813801ause correct content-type when overwriting and copying files52ed8a7add content-type test case6412860check file /etc/mime.types exist to decide run check_content_type test case📊 Changes
3 files changed (+37 additions, -15 deletions)
View changed files
📝
src/curl.cpp(+12 -9)📝
test/integration-test-main.sh(+11 -2)📝
test/test-utils.sh(+14 -4)📄 Description
When overwriting and copying a file, we need to use /etc/mime.types to decide the file Content-Type, rather than cached meta Content-Type。
Details
When overwriting and copying files, s3fs use the original file Content-Type meta cache,the cached Content-Type may be not correct, for example the file upload by a machine doest not have file /etc/mine.types。So in order to allow user fixed the wrong Content-Type, we need to use /etc/mime.types to decide the file Content-Type。
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.