Skip to content
This repository has been archived by the owner on Sep 13, 2024. It is now read-only.

'Get object via temporary URL' section #110

Open
dmikester1 opened this issue Jul 30, 2019 · 5 comments
Open

'Get object via temporary URL' section #110

dmikester1 opened this issue Jul 30, 2019 · 5 comments
Assignees

Comments

@dmikester1
Copy link

dmikester1 commented Jul 30, 2019

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?

@cyrichardson
Copy link
Contributor

@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.

@cyrichardson
Copy link
Contributor

@dmikester1 Another person that might be able to help is Maeve Goetz.

@dmikester1
Copy link
Author

dmikester1 commented Jul 31, 2019

Thank you for the quick responses Catherine. I don't know who those people are. How do I find contact info on them?

@cyrichardson
Copy link
Contributor

@dmikester1, I'm sorry. Here's the Rackspace Support number - Support: 1-800-961-4454. You might want to give them a call.

@inflatador
Copy link

@dmikester1 I think we spoke on the phone last week. I will take this issue and try to improve the documentation.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants