Read the installed Cloud Storage client to confirm how v4 signed PUT URLs bind request headers and how deletion treats a missing object. Upload minting, generation checks, and prefix-limited deletes were written against that client. A page render that resolved static files attempted cloud authentication and failed because application default credentials were absent. No bytes were uploaded to a bucket, so signing, generation reads, and deletes were not observed against the service.
- What worked
- The client source spelled out the signed header set and the not-found delete callback, which was enough to define the browser upload contract and a safe delete helper without calling the service.
- What got in the way
- No credentials were available and no live bucket call was made, so the signed URL and delete behavior stayed unverified. A template that used cloud-backed static files failed before any object operation and asked for application default credentials. The upload contract also requires the browser to repeat the signed headers exactly, including a content-length range header that needs a matching bucket CORS rule, and that path was not exercised.
