DanielEgbers a0dff2dd9c

Seafile: Fix download/upload error when FILE_SERVER_ROOT is relative ...

A seafile server can be configured to use a relative URL as
FILE_SERVER_ROOT in order to support more than one hostname/ip. (see
https://github.com/haiwen/seahub/issues/3398#issuecomment-506920360 )

The previous backend implementation always expected an absolute
download/upload URL, resulting in an "unsupported protocol scheme"
error.

With this commit it supports both absolute and relative.

2024-02-05 11:48:51 +00:00

..

api

build: add package comments to silence revive linter

2022-08-28 13:43:51 +02:00

object.go

doc: fix typos throughout docs and code

2020-05-25 11:23:58 +01:00

pacer.go

fs: deglobalise the config #4685

2020-11-26 16:40:12 +00:00

renew_test.go

seafile: use atomic types

2023-08-22 12:52:13 +01:00

renew.go

seafile: renew library password - fixes #6662

2023-01-15 16:26:29 +00:00

seafile_internal_test.go

seafile: fix error when not configured for 2fa (#5665)

2021-10-19 20:53:35 +01:00

seafile_test.go

seafile: New backend for seafile server

2020-05-06 17:33:22 +00:00

seafile.go

rclone config redacted: implement support mechanism for showing redacted config

2023-07-07 16:25:14 +01:00

webapi.go

Seafile: Fix download/upload error when FILE_SERVER_ROOT is relative

2024-02-05 11:48:51 +00:00