Storage.googleapis.com or storage.cloud.google.com for signed URL

Question

Storage.googleapis.com or storage.cloud.google.com for signed URL

I sign the GET url to GAE and pass it to my client app so that it can download the file from google repository directly. If the client application sends a request for the storage.googleapis.com file, it receives a SignatureDoesNotMatch response. It works if the request is sent to storage.cloud.google.com (still gets 302, but I think it will work if redirected).

But if I create a signed url in my local app (not in GAE) then the request works (the file is loaded) using storage.googleapis.com.

I would like to know what is the correct url to send a signed url request and why the difference in behavior is between the GAE signed url and the url signed local app.

Getting started with PUT requests, the URL signed generated from the GAE request for the PUT request does not work (403, 405) with any domains, although the local URL signed app does. I am confused by this strange behavior.

+3

google-app-engine google-cloud-storage

user3787910 16 Aug 14 at 18:58

source to share

No one has answered this question yet

Check out similar questions:

five

GSUTIL Signed PUT URL for Google Cloud Storage Failed

2

Force upload to GCS via App Engine using signed url

1

Google storage php client: unable to create object by hosting signed url

1

AppEngine Safari "Failed to load resource: loading frame is interrupted" (but still loading files)

1

GCS default logoff billing

1

C # + Signed Google Store URL: The request signature we calculated does not match the signature you provided

1

Using URL-Signed Versions in Google Cloud Storage

1

Failed to create signed url in Engine app

0

Failed to upload files successfully using signed url to google cloud. Storage from Advanced REST Client

0

Signed Google Cloud Feature Gives 403 SignatureDoesNotMatch

Storage.googleapis.com or storage.cloud.google.com for signed URL

More articles: