Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not set retry flag on ForbiddenException #163

Merged
merged 1 commit into from
Sep 3, 2020

Conversation

juliushaertl
Copy link
Member

@juliushaertl juliushaertl commented Sep 3, 2020

For nextcloud/server#22556

From owncloud/core#20494 i assumed that the retry was introduced to indicate that clients should try to sync again at a later point, so I think it makes sense to not set this for files_accesscontrol thrown ForbiddenExceptions.

Signed-off-by: Julius Härtl <jus@bitgrid.net>
@nickvergessen
Copy link
Member

Well there is a request time option on access control, or your IP could change. But I tend to agree it makes no sense in most cases.

@blizzz
Copy link
Member

blizzz commented Sep 3, 2020

It sounds to be a corner case in several directions, i.e. already uploading into restricted directories. If avoiding the chance to have stray part files is more important than to keep the state in those other conditions, then yes, sure. Will take away a bit of conformability with those edge cases. I arrive at the same conclusion as @nickvergessen.

@blizzz blizzz merged commit 44a7a5b into master Sep 3, 2020
@delete-merged-branch delete-merged-branch bot deleted the bugfix/noid/retry-forbidden branch September 3, 2020 10:57
@juliushaertl
Copy link
Member Author

/backport to stable19

@juliushaertl
Copy link
Member Author

/backport to stable18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants