cloudreve/Cloudreve

使用davfs2 挂载到本地目录, 存储策略为cos, 在copy文件时候由于服务侧301重定向, 导致copy失败

Open

#1759 opened on Jul 3, 2023

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Go (21,463 stars) (3,383 forks)batch import
enhancementgood first issue

Description

Describe the bug 如题

To Reproduce Steps to reproduce the behavior:

  1. mount -t davfs -o noexec,ro https://xxx/dav/ /data/

Expected behavior 当后端存储为对象存储时，不要重定向为对象存储的url，而是由服务器代理传输。或者可由配置文件调整，以使兼容性更好。

Desktop (please complete the following information):

  • docker: 20.10.21
  • image: cloudreve/cloudreve:latest

Contributor guide

Tech stack
gorest api
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go basicsHTTP redirect understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the WebDAV handler in the Go code, specifically the part that handles file copy operations. Look for where the 301 redirect occurs, likely in the storage adapter for COS (Tencent Cloud Object Storage). Check if there is a configuration option to force proxy mode vs redirect. Review any existing comments or linked PRs for context.