OpenListTeam / OpenListTeam/OpenList
[BUG] mediafile session非常容易过期
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24.7k
- Forks
- 2.3k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 36
Description
Please confirm the following
-
I have read and agree to AGPL-3.0 Section 15 .
The program is provided "as is" without any warranties; you bear all risks of using it. -
I have read and agree to AGPL-3.0 Section 16 .
The copyright holders and distributors are not liable for any damages resulting from the use or inability to use the program. -
I confirm my description is clear, polite, helps developers quickly locate the issue, and complies with community rules.
-
I have read the OpenList documentation.
-
I confirm there are no duplicate issues or discussions.
-
I confirm this is an
OpenListissue, not caused by other reasons (such as network, dependencies, or operation). -
I believe this issue must be handled by
OpenListand not by a third party. -
I confirm this issue is not fixed in the latest version.
OpenList Version (required)
v4.1.9
Storage Driver Used (required)
mediafire
Bug Description (required)
使用cookie挂载mediafire 后, 大概1个小时 session就过期了 导致无法显示文件
网页端并没有主动logout mediafire , 这么容易过期 基本处于不可用状态
Logs (required)
failed get objs: failed to list objs: MediaFire API error:
Configuration File Content (required)
failed get objs: failed to list objs: MediaFire API error:
Reproduction Link (optional)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the mediafire storage driver in OpenList v4.1.9 using a cookie-based mount, then inspect the resulting MediaFire API error after the session expires. Done means the mounted storage continues listing files after roughly an hour without requiring an active logout or reauthentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100