Change default mimetype detection for storage backends to only use filename #5965
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👍 |
|
@PVince81 @schiesbn What do you think? |
|
Does it mean that even for local storages we don't use the "file" command any more ? |
|
@PVince81 Yes. That's the idea. I don't think we need it at all. |
|
Ok I'll test this with SFTP. I expect the scanning should become almost as fast as I observed yesterday in #5954 |
|
Test passed. |
|
70 pics, 7 seconds to scan (instead of minutes) ! Well done ! 👍 |
PVince81
pushed a commit
that referenced
this pull request
Nov 20, 2013
Change default mimetype detection for storage backends to only use filename
This was referenced Nov 20, 2013
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This speeds up mimetype detection for external storages in some cases.
cc @karlitschek @DeepDiver1975