400 Bad Request on Storage.copy #1237
Copy link
Copy link
Closed
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.
Description
Activity
- addedapi: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.
on Sep 9, 2016 For issues like this, the service team finds it super helpful if you can also specify one or more example requests' HTTP log, with request and response headers and body, and any timing information. Scrub the
Authorizationheader or any OAuth token in the request if posting to public fora.For reference: the team in charge of this has been informed and the issue is being taken care of.
This was fixed on the service-side. I'll reopen in case we experience again.
- added a commit that references this issue
on Jun 23, 2022 - added a commit that references this issue
on Sep 15, 2022 - added a commit that references this issue
on Dec 22, 2025 - added a commit that references this issue
on Jan 6, 2026 - added a commit that references this issue
on Feb 24, 2026 - added a commit that references this issue
on Mar 11, 2026 - added a commit that references this issue
on Mar 12, 2026 - added a commit that references this issue
on Mar 23, 2026 - added a commit that references this issue
on Mar 30, 2026 - added a commit that references this issue
on Apr 1, 2026 - added 2 commits that reference this issue
on Apr 29, 2026
Metadata
Metadata
Assignees
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.
I started seeing this today. Sometimes our integration tests fail with the following error:
The code that causes the error is the following:
What's weird is that we never experienced this error before today and it does not occur systematically. @Capstan any idea?