It's an interesting thought, but I'd first be a little concerned about public swift clusters being abused by this. However, that's with about 10 seconds of thought and it may not be a major concern.

Instead of doing 3xx redirects, you can use the existing large-object manifest files for this. You can upload, eg, user_guide_latest.pdf, and have that reference a specific file on the back end (eg versions/user_guide_20130301.pdf). Then you can stage new versions and update the link very quickly.

Docs for large object support: http://docs.openstack.org/developer/s...

--John

On Feb 28, 2013, at 2:46 PM, Tim Newsome question223106@answers.launchpad.net wrote:

New question #223106 on OpenStack Object Storage (swift): https://answers.launchpad.net/swift/+...

Can I upload a redirect to Swift?

The problem I have is that I have a data store of a lot of files, many of which are identical. When a client requests a file, I would like to redirect that client to the canonical URL for that file (also stored in Swift). This allows clients to maximize their cache hit rate, and prevents them from storing multiple copies of the same thing in their cache.

As a quick example, I'd like to do something like: curl –X PUT -i \ -T JingleRocky.jpg \ https://storage.swiftdrive.com/v1/CF_... curl –X PUT -i \ -T /dev/null \ -H "X-Object-Meta-Redirect-303: https://storage.swiftdrive.com/v1/CF_... \ https://storage.swiftdrive.com/v1/CF_...

Then when I GET https://storage.swiftdrive.com/v1/CF_... , Swift would return an HTTP 303 return code, with a redirect to https://storage.swiftdrive.com/v1/CF_... .

Is this possible? If not, how much work would you estimate this is to implement by an experienced python programmer? Would such a change be considered for inclusion into the main project?

Thank you, Tim

---

You received this question notification because you are a member of Swift Core, which is an answer contact for OpenStack Object Storage (swift).

One could write a custom Swift middleware to handle this. The middleware would pass the request on through to the proxy, and then if (a) the request is a GET for an object and (b) the response headers have X-Meta-Object-Redirect-303 in them, then return a redirect response instead.

Note that if you wanted to add this to Swift, you'd almost certainly be told to write it as a middleware, so "write some middleware" does not imply "keep it out of core Swift." The above suggestion makes no statements about the suitability of such a middleware for inclusion in core Swift, either positive or negative.