Yes, that's correct. I'm writing a server app that exposes the cloud container via webdav. In this particular case, the client is an in-browser webdav file browser written in javascript. I do have control of the js webdav client, but I was hoping to redirect the browser client to a signed url in order to download the blob for a webdav GET. Alternatively, the webdav resource url could just be the signed url. Proxying through my server app also works, but it would be preferable to download directly from the provider.
Eventually, there will be an applet or other webdav client to perform the multi-part uploads for large files. That client app would also need to use the signed urls, I would imagine. Am I going about this wrong? Would you recommend a different approach? Kevin On Fri, Aug 23, 2013 at 5:22 PM, Andrew Phillips <andr...@apache.org> wrote: >> I was hoping to return a 302 or 307 redirect the browser to the >> appropriate endpoint. The Auth header isn't included in the redirect, >> so query parameters are required instead. > > > Just to clarify: you're writing a *server-side* app and are trying so send > *clients* to a different URL which is pre-signed? Do you have control of the > client app in any way? > > ap
