Proxy_pass Directive !!

[shahzaib shahzaib]

>>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.

@itpp, you're always the light of hope in darkness :-).Thats the exact
solution i need, rewrite is not recommended in our solution because we're
using View directive of bind where same domain test.com will resolve to
edge as well as origin server on the basis of client's ip. So i cannot
rewrite test.com back to test.com. You mentioned the solution
HTTP-EQUIV="REFRESH" . Is that fine to use this method also, could you tell
me how to use it with origin ip in nginx ? So client will resend the
request to origin instead of edge.




On Sun, Jul 20, 2014 at 12:15 AM, Payam Chychi <pchychi at gmail.com> wrote:

>  Use a resirect, keep it clean, simple, and compliant
>
> Why waste reaources when you dont have to?
>
> --
> Payam Chychi
> Network Engineer / Security Specialist
>
> On Saturday, July 19, 2014 at 10:47 AM, Anoop Alias wrote:
>
>
>
>
> The Proxying server does not download the entire file ;save it to disk and
> then serve from that .
>
> The proxy simply buffers the content (which is config manageable) and
> serve the end user (browser ) .So the proxy will not face a high disk i/o
> load like the origin ..
>
>
>
> --
> *Anoop P Alias*
> GNUSYS <http://gnusys.net>
>  _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140720/500eaa9f/attachment.html>