[PR #2510] [MERGED] s3 signv4 support pefixed s3 hosts #2587

New issue

Closed

opened 2026-03-04 02:06:18 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 02:06:18 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/2510
Author: @fenos
Created: 8/8/2024
Status: ✅ Merged
Merged: 8/17/2024
Merged by: @ggtakec

Base: master ← Head: s3/support-endpoint-with-uris

📝 Commits (1)

25cf925 s3 signv4 support uri endpoints

📊 Changes

2 files changed (+34 additions, -1 deletions)

View changed files

📝 src/curl.cpp (+32 -1)
📝 src/curl.h (+2 -0)

📄 Description

Relevant Issue (if applicable)

When trying to connect to a compatible S3 server that is serving the S3 API under a URI prefix, ex:

https://storage.example/s3

s3fs fails to compute the SignV4; specifically on capturing the URI of the s3host.

Details

This PR will instead use the prefix (if any) when calculating the SignV4 uri; enabling support for custom S3 providers served on a URI.

If no prefix is given in the custom url, the current behaviour of using "/" is maintained.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/2510 **Author:** [@fenos](https://github.com/fenos) **Created:** 8/8/2024 **Status:** ✅ Merged **Merged:** 8/17/2024 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `s3/support-endpoint-with-uris` --- ### 📝 Commits (1) - [`25cf925`](https://github.com/s3fs-fuse/s3fs-fuse/commit/25cf92532070a2156baf67df89293403427b4ba5) s3 signv4 support uri endpoints ### 📊 Changes **2 files changed** (+34 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/curl.cpp` (+32 -1) 📝 `src/curl.h` (+2 -0) </details> ### 📄 Description  ### Relevant Issue (if applicable)  When trying to connect to a compatible S3 server that is serving the S3 API under a URI prefix, ex: ``` https://storage.example/s3 ``` `s3fs` fails to compute the SignV4; specifically on capturing the URI of the s3host. ### Details  This PR will instead use the prefix (if any) when calculating the SignV4 uri; enabling support for custom S3 providers served on a URI. If no prefix is given in the custom `url`, the current behaviour of using "/" is maintained. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>