diff options
| author | wxiaoguang <wxiaoguang@gmail.com> | 2023-03-28 23:10:24 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-28 11:10:24 -0400 |
| commit | 5727056ea109eb04ee535b981349cdfb44df9fae (patch) | |
| tree | af2b96f7b7871dd3d07169642b6234369c032632 /tests/pgsql.ini.tmpl | |
| parent | 6a0ef71984b9246fc1bb378caaa614f3dedaa9e9 (diff) | |
| download | gitea-5727056ea109eb04ee535b981349cdfb44df9fae.tar.gz gitea-5727056ea109eb04ee535b981349cdfb44df9fae.zip | |
Make minio package support legacy MD5 checksum (#23768)
A feedback from discord:
https://discord.com/channels/322538954119184384/561007778139734027/1090185427115319386
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.
I guess this needs to be backported because IIRC we 1.19 and 1.20 are
using similar minio package.
The minio package code for SendContentMD5 looks like this:
<details>
<img width="755" alt="image"
src="https://user-images.githubusercontent.com/2114189/228186768-4f2f6f67-62b9-4aee-9251-5af714ad9674.png">
</details>
Diffstat (limited to 'tests/pgsql.ini.tmpl')
| -rw-r--r-- | tests/pgsql.ini.tmpl | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/pgsql.ini.tmpl b/tests/pgsql.ini.tmpl index fbfbae7c68..15349aa4c2 100644 --- a/tests/pgsql.ini.tmpl +++ b/tests/pgsql.ini.tmpl @@ -125,6 +125,7 @@ MINIO_SECRET_ACCESS_KEY = 12345678 MINIO_BUCKET = gitea MINIO_LOCATION = us-east-1 MINIO_USE_SSL = false +MINIO_CHECKSUM_ALGORITHM = md5 [packages] ENABLED = true |