-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to enable CDN: KeyError 'x-cdn-uri' ? wrong type of cloudfiles container? #3
Comments
I have the same problem. I did not find the time to investigate that issue. It's probably a bug in libcloud and/or rackspace. In the mean time you can activate the public CDN manually in the rackspace cloud web interface. You only need to do it once per container. |
Use a short TTL, e.g. 15 min if you want you to be able to see an index.html file that is not too old. |
I also just turned on the directory listing feature (rather than uploading an index.html). Is there a reason to use the CDN rather than just a normal cloud files repository? I can't recall if the cost is any different. (anyway, feel free to do what you want with this issue!) |
I don't know how to do that. Where did you see such an option?
I understood that CDN was the only way to turn a cloud files container into a public HTTP / HTML website suitable for consumption by |
You're right -- I thought there was a public + not cdn option available. As for the directory listing, the relevant option is
you have to use an auth token rather than the api key, but getting that isn't so bad. I can confirm that the directory listing works fine for doing |
Alright I did not know about that. It would be great to send a PR to apache libcloud to add it as an extension the rackspace provider (using the |
Uploading works, but I get this error:
I might have setup my cloudfiles incorrectly.
Just noting it here. Minor problem compared to the last one.
The text was updated successfully, but these errors were encountered: