<div class="gmail_quote">On May 10, 2014 6:00 AM, <<a href="mailto:nginx-request@nginx.org">nginx-request@nginx.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Send nginx mailing list submissions to<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:nginx-request@nginx.org">nginx-request@nginx.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:nginx-owner@nginx.org">nginx-owner@nginx.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of nginx digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Caching servers in Local ISPs !! (itpp2012)<br>
2. Re: subs filter error (Jonathan Matthews)<br>
3. Re: Caching servers in Local ISPs !! (Steve Holdoway)<br>
4. Re: Caching servers in Local ISPs !! (shahzaib shahzaib)<br>
5. Re: subs filter error (Tom McLoughlin)<br>
6. Re: Caching servers in Local ISPs !! (itpp2012)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 09 May 2014 16:01:46 -0400<br>
From: "itpp2012" <<a href="mailto:nginx-forum@nginx.us">nginx-forum@nginx.us</a>><br>
To: <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
Subject: Re: Caching servers in Local ISPs !!<br>
Message-ID:<br>
<<a href="mailto:c081cd6fb43e5b579a74dcda519cecf6.NginxMailingListEnglish@forum.nginx.org">c081cd6fb43e5b579a74dcda519cecf6.NginxMailingListEnglish@forum.nginx.org</a>><br>
<br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
> So on easy note, i would have to assign those machines the preferred<br>
> dns<br>
> and use rsync on regular basis in order to make identical data<br>
> between<br>
> local caching machines and main front end content servers ?<br>
<br>
Yep.<br>
<br>
> What if a client request a video which is not in local caching server<br>
> ?<br>
<br>
You need to maintain a cache index on each cache machine in order to<br>
determine what is available to the users, for most content you need to do<br>
this anyway since not all content can legally be everywhere and you also<br>
might want to customize what you present for each region.<br>
<br>
> Does nginx has the configuration for it to check the files locally and<br>
> then<br>
> forward the request to main content servers if requested file is not<br>
> cached<br>
> locally ?<br>
<br>
There are many ways to do this with nginx and Lua but a independent cache<br>
index would be much better, with it you can do much more like redirect a<br>
content source from elsewhere depending on load and demand. You simply feed<br>
nginx the cache index. A very simplistic cache index system is abusing a<br>
local (local to nginx) dns server, assign local IP's to resources and change<br>
them according to load and demand. Again for a local DNS you can assign<br>
whatever you want to a dns name, with a local ttl of 15 seconds and nginx<br>
loadbalancing between 4 regional resources it will be peanuts to change the<br>
load based on demand (provided you have monitoring in place which can act on<br>
such data). Basically a DIY BGP :)<br>
<br>
Posted at Nginx Forum: <a href="http://forum.nginx.org/read.php?2,249997,250002#msg-250002" target="_blank">http://forum.nginx.org/read.php?2,249997,250002#msg-250002</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 9 May 2014 23:05:41 +0100<br>
From: Jonathan Matthews <<a href="mailto:contact@jpluscplusm.com">contact@jpluscplusm.com</a>><br>
To: <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
Subject: Re: subs filter error<br>
Message-ID:<br>
<<a href="mailto:CAKsTx7Cy2ahdy05DOJo00_ddRFoqy-oyQBNv4BdU-QOh5UJWtQ@mail.gmail.com">CAKsTx7Cy2ahdy05DOJo00_ddRFoqy-oyQBNv4BdU-QOh5UJWtQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On 9 May 2014 13:36, Tom McLoughlin <<a href="mailto:me@tommehm.com">me@tommehm.com</a>> wrote:<br>
> I keep getting this error every time someone loads a page.<br>
> subs filter header ignored, this may be a compressed response. while<br>
> reading response header from upstream, client: xx.xx.xx.xx, server: ,<br>
> request: "GET /search/sharepoint/0/7/0 HTTP/1.1", upstream:<br>
> "<a href="http://194.71.107.80:80/search/sharepoint/0/7/0" target="_blank">http://194.71.107.80:80/search/sharepoint/0/7/0</a>", host: "<a href="http://tpb.rtbt.me" target="_blank">tpb.rtbt.me</a>",<br>
> referrer: "<a href="http://tpb.rtbt.me/search/sharepoint/0/99/" target="_blank">http://tpb.rtbt.me/search/sharepoint/0/99/</a>"<br>
<br>
So why not stop the upstream responding with a compressed response?<br>
<br>
I know how to do this for TPB, having written a *14* line nginx config<br>
to do exactly the same thing, reverse proxying TPB for .. academic<br>
reasons. But you're trying to make money off them, so I don't feel<br>
like sharing. I'll let you figure it out. It's really not difficult.<br>
<br>
J<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sat, 10 May 2014 16:24:57 +1200<br>
From: Steve Holdoway <<a href="mailto:steve@greengecko.co.nz">steve@greengecko.co.nz</a>><br>
To: <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
Subject: Re: Caching servers in Local ISPs !!<br>
Message-ID: <1399695897.24481.647.camel@steve-new><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
You might want to look at lsyncd - a GZSOC project - to ease the<br>
synchronisation. I have had good results with it.<br>
<br>
Steve<br>
On Sat, 2014-05-10 at 00:22 +0500, shahzaib shahzaib wrote:<br>
> @itpp thanks for replying.<br>
><br>
><br>
> So on easy note, i would have to assign those machines the preferred<br>
> dns and use rsync on regular basis in order to make identical data<br>
> between local caching machines and main front end content servers ?<br>
><br>
><br>
> What if a client request a video which is not in local caching<br>
> server ? Does nginx has the configuration for it to check the files<br>
> locally and then forward the request to main content servers if<br>
> requested file is not cached locally ?<br>
><br>
><br>
> I need a bit of guidance in order to configure nginx this way.<br>
><br>
><br>
> Shahzaib<br>
><br>
><br>
><br>
><br>
> On Fri, May 9, 2014 at 11:49 PM, itpp2012 <<a href="mailto:nginx-forum@nginx.us">nginx-forum@nginx.us</a>><br>
> wrote:<br>
> Its quite simple, think of it this way, a DNS entry does not<br>
> have to point<br>
> to the same IP everywhere.<br>
><br>
> Place your cache machines at a ISP, have them assign its IP to<br>
> your<br>
> preferred dns name, thats about it.<br>
><br>
> The rest like distribution works like a reverse riverbed with<br>
> a master<br>
> mirror, rsync or the likes.<br>
><br>
> And of course this can all be done with nginx at all<br>
> locations.<br>
><br>
> Posted at Nginx Forum:<br>
> <a href="http://forum.nginx.org/read.php?2,249997,250000#msg-250000" target="_blank">http://forum.nginx.org/read.php?2,249997,250000#msg-250000</a><br>
><br>
> _______________________________________________<br>
> nginx mailing list<br>
> <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
> <a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> nginx mailing list<br>
> <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
> <a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
<br>
--<br>
Steve Holdoway BSc(Hons) MIITP<br>
<a href="http://www.greengecko.co.nz" target="_blank">http://www.greengecko.co.nz</a><br>
Linkedin: <a href="http://www.linkedin.com/in/steveholdoway" target="_blank">http://www.linkedin.com/in/steveholdoway</a><br>
Skype: sholdowa<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Sat, 10 May 2014 14:19:37 +0500<br>
From: shahzaib shahzaib <<a href="mailto:shahzaib.cb@gmail.com">shahzaib.cb@gmail.com</a>><br>
To: <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
Subject: Re: Caching servers in Local ISPs !!<br>
Message-ID:<br>
<<a href="mailto:CAD3xhrPbC-F_8cY2t%2B3JqspL3-g_RZM4sPYd7p40WxFcvboqSA@mail.gmail.com">CAD3xhrPbC-F_8cY2t+3JqspL3-g_RZM4sPYd7p40WxFcvboqSA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thanks for replying guyz.<br>
<br>
Can i use nginx (origin and edge) ? As the question in following link.<br>
<br>
<a href="http://stackoverflow.com/questions/10024981/distributed-cached-mp4-pseudostreaming-seeking-with-nginx" target="_blank">http://stackoverflow.com/questions/10024981/distributed-cached-mp4-pseudostreaming-seeking-with-nginx</a><br>
<br>
If i use the origin and edge method, i think i'll change my application<br>
codes to redirect local country traffic to edge webservers (ISP caching<br>
server for video files) and that edge server will check if the requested<br>
file is not in cache and it'll fetch the requested video file from origin<br>
web-server located in U.S and cache it to local.<br>
<br>
For this procedure,<br>
<br>
I'll have to configure DNS A entries against local ISP caching servers and<br>
put those DNS to my application code to stream videos from those LOCAL<br>
CACHING SERVERS for specific country.<br>
<br>
Please correct me if i am wrong.<br>
<br>
<br>
<br>
<br>
<br>
<br>
On Sat, May 10, 2014 at 9:24 AM, Steve Holdoway <<a href="mailto:steve@greengecko.co.nz">steve@greengecko.co.nz</a>>wrote:<br>
<br>
> You might want to look at lsyncd - a GZSOC project - to ease the<br>
> synchronisation. I have had good results with it.<br>
><br>
> Steve<br>
> On Sat, 2014-05-10 at 00:22 +0500, shahzaib shahzaib wrote:<br>
> > @itpp thanks for replying.<br>
> ><br>
> ><br>
> > So on easy note, i would have to assign those machines the preferred<br>
> > dns and use rsync on regular basis in order to make identical data<br>
> > between local caching machines and main front end content servers ?<br>
> ><br>
> ><br>
> > What if a client request a video which is not in local caching<br>
> > server ? Does nginx has the configuration for it to check the files<br>
> > locally and then forward the request to main content servers if<br>
> > requested file is not cached locally ?<br>
> ><br>
> ><br>
> > I need a bit of guidance in order to configure nginx this way.<br>
> ><br>
> ><br>
> > Shahzaib<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On Fri, May 9, 2014 at 11:49 PM, itpp2012 <<a href="mailto:nginx-forum@nginx.us">nginx-forum@nginx.us</a>><br>
> > wrote:<br>
> > Its quite simple, think of it this way, a DNS entry does not<br>
> > have to point<br>
> > to the same IP everywhere.<br>
> ><br>
> > Place your cache machines at a ISP, have them assign its IP to<br>
> > your<br>
> > preferred dns name, thats about it.<br>
> ><br>
> > The rest like distribution works like a reverse riverbed with<br>
> > a master<br>
> > mirror, rsync or the likes.<br>
> ><br>
> > And of course this can all be done with nginx at all<br>
> > locations.<br>
> ><br>
> > Posted at Nginx Forum:<br>
> > <a href="http://forum.nginx.org/read.php?2,249997,250000#msg-250000" target="_blank">http://forum.nginx.org/read.php?2,249997,250000#msg-250000</a><br>
> ><br>
> > _______________________________________________<br>
> > nginx mailing list<br>
> > <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
> > <a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > nginx mailing list<br>
> > <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
> > <a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
><br>
> --<br>
> Steve Holdoway BSc(Hons) MIITP<br>
> <a href="http://www.greengecko.co.nz" target="_blank">http://www.greengecko.co.nz</a><br>
> Linkedin: <a href="http://www.linkedin.com/in/steveholdoway" target="_blank">http://www.linkedin.com/in/steveholdoway</a><br>
> Skype: sholdowa<br>
><br>
> _______________________________________________<br>
> nginx mailing list<br>
> <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
> <a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mailman.nginx.org/pipermail/nginx/attachments/20140510/b44f1a9a/attachment-0001.html" target="_blank">http://mailman.nginx.org/pipermail/nginx/attachments/20140510/b44f1a9a/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Sat, 10 May 2014 10:53:17 +0100<br>
From: Tom McLoughlin <<a href="mailto:me@tommehm.com">me@tommehm.com</a>><br>
To: <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
Subject: Re: subs filter error<br>
Message-ID: <<a href="mailto:536DF70D.2050302@tommehm.com">536DF70D.2050302@tommehm.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
That's the only upstream I'm aware of that works with proxies.<br>
<br>
On 09/05/2014 23:05, Jonathan Matthews wrote:<br>
> On 9 May 2014 13:36, Tom McLoughlin <<a href="mailto:me@tommehm.com">me@tommehm.com</a>> wrote:<br>
>> I keep getting this error every time someone loads a page. subs<br>
>> filter header ignored, this may be a compressed response. while<br>
>> reading response header from upstream, client: xx.xx.xx.xx,<br>
>> server: , request: "GET /search/sharepoint/0/7/0 HTTP/1.1",<br>
>> upstream: "<a href="http://194.71.107.80:80/search/sharepoint/0/7/0" target="_blank">http://194.71.107.80:80/search/sharepoint/0/7/0</a>",<br>
>> host: "<a href="http://tpb.rtbt.me" target="_blank">tpb.rtbt.me</a>", referrer:<br>
>> "<a href="http://tpb.rtbt.me/search/sharepoint/0/99/" target="_blank">http://tpb.rtbt.me/search/sharepoint/0/99/</a>"<br>
><br>
> So why not stop the upstream responding with a compressed<br>
> response?<br>
><br>
> I know how to do this for TPB, having written a *14* line nginx<br>
> config to do exactly the same thing, reverse proxying TPB for ..<br>
> academic reasons. But you're trying to make money off them, so I<br>
> don't feel like sharing. I'll let you figure it out. It's really<br>
> not difficult.<br>
><br>
> J<br>
><br>
> _______________________________________________ nginx mailing list<br>
> <a href="mailto:nginx@nginx.org">nginx@nginx.org</a> <a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Sat, 10 May 2014 06:39:55 -0400<br>
From: "itpp2012" <<a href="mailto:nginx-forum@nginx.us">nginx-forum@nginx.us</a>><br>
To: <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
Subject: Re: Caching servers in Local ISPs !!<br>
Message-ID:<br>
<<a href="mailto:461b89f745fbc7e6c616c28d3fa6a39f.NginxMailingListEnglish@forum.nginx.org">461b89f745fbc7e6c616c28d3fa6a39f.NginxMailingListEnglish@forum.nginx.org</a>><br>
<br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
See <a href="http://en.wikipedia.org/wiki/Content_delivery_network" target="_blank">http://en.wikipedia.org/wiki/Content_delivery_network</a><br>
and <a href="http://en.wikipedia.org/wiki/File:Akamaiprocess.png" target="_blank">http://en.wikipedia.org/wiki/File:Akamaiprocess.png</a><br>
<br>
Make yourself a HLD (high level design) before getting to technology.<br>
<br>
Posted at Nginx Forum: <a href="http://forum.nginx.org/read.php?2,249997,250007#msg-250007" target="_blank">http://forum.nginx.org/read.php?2,249997,250007#msg-250007</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
<br>
End of nginx Digest, Vol 55, Issue 26<br>
*************************************<br>
</blockquote></div>