Hello!

On Thu, Apr 11, 2013 at 11:08:47AM -0400, winniethepooh wrote:

> Maxim Dounin Wrote:
> -------------------------------------------------------
> > Hello!
> >
> > On Thu, Apr 11, 2013 at 04:15:02AM -0400, winniethepooh wrote:
> >
> > It's not clear why you added "x.x.x.x" to the upstream block if
> > it's not an upstream but the same server. Obvious solution would
> > be to remove it.
> >
> > If you try to implement "check the local disk, and if the file
> > isn't there - proxy to dropbox" logic, correct solution would be
> > to use something similar to an example provided at
> > http://nginx.org/r/error_page:
> >
> > location / {
> > error_page 404 = @fallback;
> > }
> >
> > location @fallback {
> > proxy_pass http://backend;
> > }
> >
> > --
> > Maxim Dounin
> > http://nginx.org/en/donation.html
>
> Hey, thanks for your reply! I have the same files stored both at
> /path/to/my/root/* and at http://dl.dropbox.com/u/#########/*. The same
> folder structure and everything.
>
> What I want is to "load balance" between dropbox and the same nginx site
> (x.x.x.x) so both places can serve files.

Ok, so you are you trying to save disk bandwidth at cost of
network one.

> Is the only way to do this to split up the proxy as one server block on one
> port (80 for example) and the actual server block hosting the files in
> another server block on a different server port (8080 for example)?
>
> Or can I modify the originally posted setup to do what I want?

Using distinct server blocks is most simple option.

--
Maxim Dounin
http://nginx.org/en/donation.html

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx