Kindly log in to use this feature. We’ll take you to the login page automatically.
LoginGeneral Tech Bugs & Fixes 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Kindly log in to use this feature. We’ll take you to the login page automatically.
LoginReady to take your education and career to the next level? Register today and join our growing community of learners and professionals.
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
manpreet
Best Answer
3 years ago
I'm following this guide and have a solution which is uploading objects to Google Cloud storage using the signed URL and the XML REST API (e.g.
curl -v -X POST $URL -F "file=@test.jpg").Unfortunately, I cannot figure out how to set the ACL on these objects such that they'll be publicly visible. I have tried using the
x-goog-aclheader (and various capitalizations in both the signed URL and request headers) and theaclquery parameter without success.I assume this must be possible, as it's referenced in the API documentation and all of the client libraries allow you to do this. I have a feeling I'm screwing something up in my URL signing method (even though the header appears in the signed URL:
https://storage.googleapis.com/foo/test.jpg?X-Goog-Algorithm=GOOG4-RSA-SHA256&X-Goog-Credential=STUFF&X-Goog-SignedHeaders=host%3Bx-goog-acl&acl=public-read&MORE-STUFF), but I'm sort of at a loss.