Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
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 misleads debugging. The real cause: the Content-Type header sent with the upload did not match the content type baked into the signed URL, so GCS rejected the request before the CORS headers were applied.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
When generating the signed URL, pass the exact Content-Type the client will upload with (e.g. image/png or application/octet-stream), and make sure the client sends that same header: users on the thread confirmed uploads work once the signed content-type matches. If you cannot know the type ahead of time, sign with application/octet-stream and upload as such.
Source: https://github.com/googleapis/nodejs-storage/issues/347
Shows how to fix gCS signed URL upload fails CORS: preflight OK, PUT rejected. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix gCS Node.js client: ADC, resumable uploads, and the signed-URL signing trap. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
When hitting a self-hosted Prisma Cloud Compute Console API (port 8083) with curl, either pass --insecure (the connection stays encrypted, you just skip identity validation) or configure Prisma Cloud Compute to use your own custom certs.