[PR #200] [MERGED] fixed fallback to sigv2 for bucket create and GCS #1394

New issue

Closed

opened 2026-03-04 01:53:43 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:53:43 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/200
Author: @ggtakec
Created: 6/20/2015
Status: ✅ Merged
Merged: 6/20/2015
Merged by: @ggtakec

Base: master ← Head: fixbug

📝 Commits (1)

966d229 fixed fallback to sigv2 for bucket create and GCS

📊 Changes

1 file changed (+66 additions, -63 deletions)

View changed files

📝 src/s3fs.cpp (+66 -63)

📄 Description

This pull request fixed following:

fallback to sigv2 when creating bucket
Modified "fallback to sigv2 on bucket create"(#180) by kahing
fixed fallback sigv2 logic for GCS.
Modified "fix v4 fallback to work correctly for GCS"(#181) by kahing
Fixed #179
do fail by timeout when connecting bucket

_{🔄 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/200 **Author:** [@ggtakec](https://github.com/ggtakec) **Created:** 6/20/2015 **Status:** ✅ Merged **Merged:** 6/20/2015 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `fixbug` --- ### 📝 Commits (1) - [`966d229`](https://github.com/s3fs-fuse/s3fs-fuse/commit/966d229787ff33f3eaa5cc4e1abeb3b963aedd61) fixed fallback to sigv2 for bucket create and GCS ### 📊 Changes **1 file changed** (+66 additions, -63 deletions) <details> <summary>View changed files</summary> 📝 `src/s3fs.cpp` (+66 -63) </details> ### 📄 Description This pull request fixed following: - fallback to sigv2 when creating bucket Modified "fallback to sigv2 on bucket create"(#180) by kahing - fixed fallback sigv2 logic for GCS. Modified "fix v4 fallback to work correctly for GCS"(#181) by kahing Fixed #179 - do fail by timeout when connecting bucket --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>