[PR #1054] [CLOSED] fix fpLazySetup REQType error; Content-Length compatible Http/1.0; MultiRead retry error #1779

New issue

Closed

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

kerem commented

2026-03-04 02:02:07 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/1054
Author: @sandmanhome
Created: 6/27/2019
Status: ❌ Closed

Base: master ← Head: mybranch

📝 Commits (1)

7c9d249 1. fpLazySetup type error; 2. PreMultipartPostRequest Content-Length header lost error when server/proxy is Http/1.0 protocol; 3. MultiRead responseCode < 0 need retry

📊 Changes

1 file changed (+3 additions, -3 deletions)

View changed files

📝 src/curl.cpp (+3 -3)

📄 Description

CreateCurlHandle REQType init error when fpLazySetup, cause retry invalid
PreMultipartPostRequest Content-Length header lost when backer server(via proxy) is Http/1.0 protocol
MultiRead responseCode < 0 need retry

_{🔄 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/1054 **Author:** [@sandmanhome](https://github.com/sandmanhome) **Created:** 6/27/2019 **Status:** ❌ Closed **Base:** `master` ← **Head:** `mybranch` --- ### 📝 Commits (1) - [`7c9d249`](https://github.com/s3fs-fuse/s3fs-fuse/commit/7c9d24949613570648e458492630433effa9e6d3) 1. fpLazySetup type error; 2. PreMultipartPostRequest Content-Length header lost error when server/proxy is Http/1.0 protocol; 3. MultiRead responseCode < 0 need retry ### 📊 Changes **1 file changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `src/curl.cpp` (+3 -3) </details> ### 📄 Description 1. CreateCurlHandle REQType init error when fpLazySetup, cause retry invalid 2. PreMultipartPostRequest Content-Length header lost when backer server(via proxy) is Http/1.0 protocol 3. MultiRead responseCode < 0 need retry --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>