Rackspace Cloud Files API: 404 Error?

It sounds like you're using the old v1.0 authentication method as shown in the API docs here . Doing so will always return your default storage location. However, with v2.0 of the API auth system as described here the authentication response will contain two different Cloud Files endpoint URLs, one for each data center.

These both point to the same API, though, so all of your other Cloud Files-related code should "just work" if you swap out your authentication code.

After further analysis, I discovered that the X-Storage-Url that was issued after authenticating was storage101.dfw1.clouddrive.com. The dfw1 indicates the data center in Dallas, but the containers I created were in Chicago. To confirm that this was the problem, I created a container at the Dallas data center and tried again – everything worked fine.

I submitted a ticket to Rackspace to have my default storage location changed to Chicago. Everything is working now.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.