gitea

History

Make minio package support legacy MD5 checksum (#23768 ) (#23770 )

Backport #23768 (no source code conflict, only some unrelated
docs/test-ini conflicts)

Some storages like:

 * https://developers.cloudflare.com/r2/api/s3/api/
 * https://www.backblaze.com/b2/docs/s3_compatible_api.html

They do not support "x-amz-checksum-algorithm" header

But minio recently uses that header with CRC32C by default. So we have
to tell minio to use legacy MD5 checksum.

2023-03-29 00:02:13 +08:00

adding-legal-pages.en-us.md

…

backup-and-restore.en-us.md

…

backup-and-restore.zh-cn.md

…

backup-and-restore.zh-tw.md

…

cmd-embedded.en-us.md

…

command-line.en-us.md

…

config-cheat-sheet.en-us.md

Make minio package support legacy MD5 checksum (#23768 ) (#23770 )

2023-03-29 00:02:13 +08:00

config-cheat-sheet.zh-cn.md

…

customizing-gitea.en-us.md

…

customizing-gitea.zh-cn.md

…

email-setup.en-us.md

…

environment-variables.en-us.md

…

environment-variables.zh-cn.md

…

external-renderers.en-us.md

…

fail2ban-setup.en-us.md

…

fail2ban-setup.zh-cn.md

…

git-lfs-support.en-us.md

…

https-support.en-us.md

…

logging-documentation.en-us.md

…

mail-templates.en-us.md

…

repo-indexer.en-us.md

…

reverse-proxies.en-us.md

…

reverse-proxies.zh-cn.md

…

search-engines-indexation.en-us.md

…

signing.en-us.md

…