to test:
upload a file text.txt
upload the the md5 named as textmd5.txt
rename the file as text.txt.md5 to see if it's possible
I did this, and it works, but that's not the way it should work.
The last step, when you say "rename the file as text.txt.md5", I did that on the server (with the Windows Explorer), not through Firefox/Chrome (since I'm not using a custom template with rename option, and the default template doesn't have any rename option). I bet if I use a custom template (with the rename function), it will work fine, since the problem is only when you upload the file (for example, if I already have a md5 file on the server, I can download it normally).
Programmatically speaking, HFS checks the file extension when you upload the file, and if it's a MD5, it rejects the file. But if I have the 'fingerprints' feature disabled, it should allow uploading .md5 files normally (check the file "main.pas" in the source code)
These are the references, on the "main.pas" file, about "MD5"...
begin
result:=validFilename(data.uploadSrc)
and not sameText(data.uploadSrc, DIFF_TPL_FILE) // never allow this
and fileMatch(getMask(), data.uploadSrc);
if not result then
data.uploadFailed:='File name or extension forbidden.';
end; // complyUploadFilter PROTECTED_FILES_MASK = 'hfs.*;*.htm*;descript.ion;*.comment;*.md5;*.corrupted';procedure TmainFrm.saveNewFingerprintsChkClick(Sender: TObject);
const
MSG = 'This option creates an .md5 file for every new calculated fingerprint.'
+#13'Use with care to get not your disk invaded by these files.';
begin
if saveNewFingerprintsChk.Checked then
msgDlg(MSG, MB_ICONWARNING);
end;Either way, if the 'fingerprints' feature is disabled, it should be possible to upload .md5 files normally (out-of-the-box, I mean, without any further configuration from the end-user). That's the way it should work, don't you think?...
