OpenListTeam / OpenListTeam/OpenList
[BUG] 分享文件时如果最最大访问次数设置为1,会出现第一次访问就直接失效:the share has expired or is no longer valid
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.
-
I have not read these checkboxes and therefore I just ticked them all, Please close this issue
OpenList Version (required)
beta
Storage Driver Used (required)
本机存储
Bug Description (required)
分享文件时,如果设置了最大访问次数,则最后一次访问会直接失效无法访问。
例如:设置最大访问次数为3,第3次访问会直接返回the share has expired or is no longer valid,分享链接失效。
最主要的影响是:如果设置最大访问次数为1,就会出现第1次访问就直接失效的情况。
Logs (required)
Configuration File Content (required)
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
No source files, tests, or entry points are named. Start by reproducing the share-limit behavior with local storage and maximum visits set to 1 or 3, then trace the share validation and visit-count handling; done means the final permitted visit succeeds and the share expires only on a subsequent visit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100