You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 13, 2024. It is now read-only.
I am hung up on the the line: bin/swift-temp-url GET 3600 $ENDPOINT/{containerName}/{objectName} {arbitraryKey}
Above it the comments say: "Create the temp_url_sig and temp_url query parameter values. OpenStack Object Storage provides the swift-temp-url script that auto-generates
the temp_url_sig and temp_url_expires query parameters. For example, you might run this command:"
What is the bin/swift-temp-url bit? I am assuming the last part starting with $ENDPOINT is the URL we hit with the GET request. And is the 3600 the port we are supposed to be using?
The text was updated successfully, but these errors were encountered:
@dmikester1 I'm a writer in the Experiences Services - Content team. It has been many years since this content has been updated in the Cloud Files API Reference. Most of the team that created it has moved on. You might check with Reagan Murley, who I believe used to work in Support in the Cloud Storage area, and see if she can direct you to someone who might be able to help you.
I am working on creating a temporary URL to access our files using the API. I have read through this section numerous time: https://developer.rackspace.com/docs/cloud-files/quickstart/#get-object
I am hung up on the the line:
bin/swift-temp-url GET 3600 $ENDPOINT/{containerName}/{objectName} {arbitraryKey}
Above it the comments say: "Create the temp_url_sig and temp_url query parameter values. OpenStack Object Storage provides the swift-temp-url script that auto-generates
the temp_url_sig and temp_url_expires query parameters. For example, you might run this command:"
What is the
bin/swift-temp-url
bit? I am assuming the last part starting with $ENDPOINT is the URL we hit with the GET request. And is the 3600 the port we are supposed to be using?The text was updated successfully, but these errors were encountered: