@Jonathon, yes you're right i should not post off-topic here, offcourse i thought as nginx has tremendous amount of capabilities and there might be alternative possibility of BGP too but i was wrong. I would be thankful if you help me on ngx-http_geo_module as it is related to nginx and help me with the following problem :-
--------------------------------------------------------------------------------------------------------------------- Our local ISP provided us with some testing ip prefixes to check nginx based caching. i.e geo { default 0; 10.0.0.0/8 1; 39.23.2.0/24 1; 112.50.192.0/18 1; } Now whenever we add the prefix 112.50.192.0/18 in geo {} , all the requests coming from the 39.23.2.0/24 and 10.0.0.0/8 returns nginx 504 gateway error and videos failed to stream. To resolve this issue, we have to remove 112.50.192.0/18 1; from geo block. On Thu, Jun 19, 2014 at 1:05 AM, Jonathan Matthews <cont...@jpluscplusm.com> wrote: > On 18 Jun 2014 20:45, "shahzaib shahzaib" <shahzaib...@gmail.com> wrote: > > > > >>why not host those file on a professional CDN instead of in-house? > > Because 80% of the traffic is from our country and 50% of that traffic > is from the ISP we're talking to and this is the reason we deployed the > caching box on this ISP edge. > > But, as this now pretty off-topic thread is repeatedly demonstrating, you > haven't deployed diddly squat. You've just chucked a server in a rack and > are having to rely on unpaid, debugging-by-email advice from an > pseudonymous mailing list to get it even near functional. Let alone > properly defined and understood. > > If your *business* needs to do this, pay a professional person or > organisation to help you like others have suggested. The alternative, which > you appear to be ending up with, is a black box of hacks known only to > yourself and potentially understood by no-one, which will SPoF on you, > personally, until you leave that organisation. You don't want that. Trust > me. > </sysadmin> > > Just my 2 cents, > Jonathan > > _______________________________________________ > nginx mailing list > nginx@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx