Conversation
A Drive API lookup that timed out or failed was reported to WebDAV clients as a 404, so QNAP HBS3 read a transient backend timeout as "Target path does not exist" and went on to re-create folders, re-upload files and skip overwrites. Lookup failures are now classified: only a real 404 or a non-EXISTS item means absent. Timeouts, 408/429/5xx and network failures return 503 with Retry-After, and a rejected session returns 502 rather than a retry loop. The cached uuid is only evicted on a confirmed 404, and the metadata mappers reject a response body they cannot map.
jzunigax2
force-pushed
the
fix/webdav-lookup-failure-status
branch
from
September 18, 2026 20:06
0e3adc0 to
1806add
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A Drive API path lookup that timed out or failed transcitiently was reported to WebDAV clients as 404 Not Found. QNAP HBS3 read a this backend timeout as "Target path does not exist" and acted on it: re-creating folders, re-uploading files, skipping overwrites. Checking logs I could verify POST /folders that would fail as the folder already existed.
So lookup failures are now classified rather than all collapsed under 404