Proxy_pass Directive !!

[B.R.]

On Sat, Jul 19, 2014 at 4:27 PM, itpp2012 <nginx-forum at nginx.us> wrote:

> shahzaib1232 Wrote:
> -------------------------------------------------------
> > Means, both server's i/o will be used if the requested file to
> > upstream is
> > 720p.mp4?
>
> Yes, what you're looking for is a way to client-rewrite the address the
> source is coming from.
>
> 1.2.3.4 -> request xx.mp4 -> edge 5.6.7.8 (I don't have that file) -> send
> client address of origin and tell client to re-initiate file request with
> origin address.
>
> How? don't ask me :)
>
​
Is there a legal problem doing that? Why the smiley?

An idea just popping out of my mind:
- To redirect the client to the origin server, a 302 answer will do, won't
it?
- If you want to restrict access to the content server (and avoid clients
to directly request content there by storing its address without having
been redirected there by edge, for example when using load-balancing),
*before* redirecting the client, on the origin server, you might record
requests incoming from edge servers (trusted/whitelisted sources), pass the
client IP address with a X-Forwarded-For (name might not be exact) header
field and allow a time-limited session for that client.

All that looks like a CDN :o)
---
*B. R.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140719/8a463d2c/attachment.html>