From c742cc41d1106c3a0bd2303d32005cbd83cfc127 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 19 Oct 2018 20:41:52 +0000 Subject: [PATCH] quoted markdown asterisks --- doc/todo/preserve_file_extensions_in_WORM_and_URL_keys.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/todo/preserve_file_extensions_in_WORM_and_URL_keys.mdwn b/doc/todo/preserve_file_extensions_in_WORM_and_URL_keys.mdwn index 57cb9333e1..c9ff47cded 100644 --- a/doc/todo/preserve_file_extensions_in_WORM_and_URL_keys.mdwn +++ b/doc/todo/preserve_file_extensions_in_WORM_and_URL_keys.mdwn @@ -1 +1 @@ -Right now, when computing a WORM key from a relative path or a URL key from a URL, if the original string is longer than a SHA256 checksum, its tail is replaced with its md5. Unfortunately, this eats up the file extension(s) at the end, causing the issues that *E backends solve. It would be better to keep the tail of the path and replace the start or the middle with the md5, preserving extensions (as configured in annex.maxextensionlength) the same way *E backends do. Maybe also, add a config option for the length beyond which the replacement-with-checksum happens? +Right now, when computing a WORM key from a relative path or a URL key from a URL, if the original string is longer than a SHA256 checksum, its tail is replaced with its md5. Unfortunately, this eats up the file extension(s) at the end, causing the issues that \*E backends solve. It would be better to keep the tail of the path and replace the start or the middle with the md5, preserving extensions (as configured in annex.maxextensionlength) the same way \*E backends do. Maybe also, add a config option for the length beyond which the replacement-with-checksum happens?