docs(cloud-sync): troubleshooting for WebDAV HTTP -1 failures - #1186
Open
Crinlorite wants to merge 1 commit into
Open
docs(cloud-sync): troubleshooting for WebDAV HTTP -1 failures#1186Crinlorite wants to merge 1 commit into
Crinlorite wants to merge 1 commit into
Conversation
…on reuse Adds a troubleshooting entry for the case where Cloud Sync reports "finished with failures" while every file actually reaches the server. The frontend logs HTTP -1 for some transfers because the response could not be read, while the server's access log shows the same requests completing with 201/204 (and 405 for MKCOL on an existing collection). This happens when a pooled connection is reused after the server closed it; Apache's default KeepAliveTimeout is 5 seconds. Documents the server-side workaround (BrowserMatch nokeepalive for the libretro user agent) and notes that a failed manifest upload leaves the local manifest stale, which surfaces as spurious conflicts on the next sync.
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.
Adds a troubleshooting entry for WebDAV Cloud Sync reporting
Cloud Sync finished with failureswhile every file actually reaches theserver.
The frontend logs
HTTP -1for some transfers because the response could notbe read, while the server's access log shows those same requests completing
normally (
201/204, and405forMKCOLon a collection that alreadyexists). This happens when a pooled connection is reused after the server has
closed it — Apache's default
KeepAliveTimeoutis 5 seconds, which a sync withmany files easily exceeds.
The entry documents the server-side workaround for Apache:
and notes that a failed manifest upload leaves the local manifest stale, which
surfaces as spurious
Conflicting change of ...on the next sync — so fixingthe first usually clears the second too.
Reported in libretro/RetroArch#19457 with the frontend and server logs side by
side.