You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
An existing folder shows "Resource not found" after the server rejected the access token #4391
I understand this is a bug report and questions should be posted in the Community Discussions
I searched issues and couldn’t find anything (or linked relevant results below)
Bug Description
When the server rejected the access token while a folder loaded, 7.2.4 went to Access denied and back into the folder after logging in again; main renews the token silently but then shows Resource not found for the existing folder until a reload.
Only a 401 for a token the client still considers valid (token invalidated on the server, clock skew after wake). A token the client knows is expired is renewed in the router guard before the load and works on both. Other loaders (shares, trash, spaces overview, search) show an empty list after a 401 on both stacks.
Regression compared with OpenCloud 7.2.4 (web 7.1.5), found in the regression test before the release. Introduced by PR #2951 (d0410c0): silent renewal on 401 without retrying the load; moved into the folder service by PR #4356 (b83af6a).
Cause: packages/web-pkg/src/services/folder/folderService.ts:117-124 calls authService.handleAuthError() on a 401 and returns without running the loader again; loaderSpace.ts:164 already set currentFolder to null, so GenericSpace.vue:204/209 renders Resource not found.
Possible fix: Let handleAuthError() report whether the token was renewed and retry the load once on success; only show the auth failure if the retry gets 401 again.
Reproduction Steps
Log in as dennis and open the personal space.
Make the server reject the access token while the client still considers it valid (test: answer the next folder PROPFIND with 401, or alter the stored access token).
Open a folder.
Expected Outcome
401, then /access-denied; Log in again returns to the folder with its content.
Actual Outcome
The silent renewal succeeds, but the folder is not loaded again: Resource not found for the existing folder until a reload.
Activity