service · inferred from evidence
GCS
A hosted object storage service where signed URLs are used for uploads and CORS configurations apply.
- GCS Node SDK: lots of socket hang up errors on batch requests
Batch file existence checks against GCS (bucket.file(fileName).exists() in batches of 20) produce lots of socket hang up errors from the @google-cloud/storage Node SDK. The SDK was not reusing connections properly, so bursts of requests exh
- GCS getSignedUrl fails: Cannot sign data without client_email
Calling getSignedUrl from the Node.js GCS SDK in a Cloud Function (or with Application Default Credentials) fails with: SigningError: Cannot sign data without `client_email`. The environment has read access to the bucket but no service-acco
- GCS signed URL upload fails CORS: preflight OK, PUT rejected
Uploading to a GCS signed URL fails CORS: the preflight request completes fine, but the actual PUT is rejected with No 'Access-Control-Allow-Origin' header is present on the requested resource. The bucket CORS config is correct, which misle
- GCS signed URLs die with SignatureDoesNotMatch days before expiry
getSignedURL() from the @google-cloud/storage Node SDK (or Firebase Functions) produces signed URLs that work for several days and then start returning 403 SignatureDoesNotMatch, even though the URL has not reached its expiry. The signing k