Re: Sticky equivalent

On Thu, Jun 19, 2014 at 9:46 AM, Aleksandar Lazic wrote: > > Am 18-06-2014 20:46, schrieb Stefanita Rares Dumitrescu: > >> Oh god 1350$ >> > > Per year. > > It's cheap compared to some other commercial Servers, from my point of > view. > ​... and it is expensive compared to the open-source Apach

Re: using 2000+ ip prefixes in nginx geo module !!

looks like i have got the issue. Any requests comes from the ip located in geo.conf will be forwarded to a domain whose ip resolve into 110.93.X.X. Now when a request comes from the ip 110.93.X.X , nginx somehow unable to proxy_pass this prefix(110.93.X.X) it to the ip 110.93.X.X and shows the bad

Re: using 2000+ ip prefixes in nginx geo module !!

Issue will only resolve once i remove 110.93.192.0/18 US; from geo.conf. On Fri, Jun 20, 2014 at 9:55 AM, shahzaib shahzaib wrote: > I removed /24 on per your suggestion and also used different code for > override but the issue persists. Modified geo.conf :- > > 39.49.59.0/24 PK; > 110.93.192.0

Re: using 2000+ ip prefixes in nginx geo module !!

I removed /24 on per your suggestion and also used different code for override but the issue persists. Modified geo.conf :- 39.49.59.0/24 PK; 110.93.192.0/18 US; 117.20.16.0/20 TW; 119.63.128.0/20 TW; 202.163.104.6/32 ARY; 203.124.63.0/24 CM; 221.132.112.0/21 TW; 110.93.192.0/24 TW; is not added

Re: http Keepalive implementation

Hello, It seems ZMQ and Nginx keep coming up in conversations lately. There seems to be differing opinions on it's performance/feasibility in production. Do you plan to open source your code? I'd be curious to look at it. On Thu, Jun 19, 2014 at 12:24 AM, prkumar wrote: > I was going through N

Re: using 2000+ ip prefixes in nginx geo module !!

These 2 overlap 110.93.192.0/24 TW; 110.93.192.0/18 TW; The /24 is within the /18. In this instance you want to remove the /24. It might be worth investigating if you've got any others that overlap. I think you can probably override with a differ

Re: using 2000+ ip prefixes in nginx geo module !!

For testing purpose, i have added only few prefixes :- geo { default 0; include geo.conf; } geo.conf 39.49.59.0/24 PK; 110.93.192.0/24 TW; 110.93.192.0/18 TW; 117.20.16.0/20 TW; 119.63.128.0/20 TW; 202.163.104.6/32 ARY; 203.124.63.0/24 CM; 221.132.112.0/21 TW; Now, whenever some ip from the li

Re: using 2000+ ip prefixes in nginx geo module !!

On 19 June 2014 19:59, shahzaib shahzaib wrote: > We've added 2000+ ip prefixes in a file "geo.conf" included in nginx vhost > by using ngx-http_geo_module and received the following warning :- > > 2014/06/19 23:52:46 [warn] 1633#0: duplicate network "103.24.96.0/22", > value: "tw", old value: "tw

using 2000+ ip prefixes in nginx geo module !!

We've added 2000+ ip prefixes in a file "geo.conf" included in nginx vhost by using ngx-http_geo_module and received the following warning :- 2014/06/19 23:52:46 [warn] 1633#0: duplicate network "103.24.96.0/22", value: "tw", old value: "tw" in /usr/local/nginx/conf/geo.conf:40 2014/06/19 23:52:46

Re: Optimization of Nginx for 128 MB RAM VPS

On Thu, Jun 19, 2014 at 1:42 AM, Yumi wrote: > If you're uploading large dumps, you may wish to increase the size of > client_max_body_size And PHP's post_max_size: http://pt2.php.net/manual/en/ini.core.php#ini.post-max-size ___ nginx mailing list ngin

RE: Download full mp4 file with proxy_cache or proxy_store !!

> we're using two servers (one proxy and one backend). Proxy server  > is using proxy_cache to cache mp4 files from backend server and working  > fine. When i stream a full video from cache, the header response gives  > me the cache-status: HIT but whenever i seek the mp4 file i.e  > http://url/tes

Re: upstream on OpenBSD not executing requests

Valentin, thank you for your insight, I am upset at myself for not noticing some obvious errors, but that's the result of my stupid schedule, which I am personally responsible for at the end. So yes, it was supposed to be 10.1.1.10 and 10.1.1.11. At this point the balancing works, I am balancing

Re: http Keepalive implementation

Hello! On Thu, Jun 19, 2014 at 01:24:53AM -0400, prkumar wrote: > I was going through NGINX source code to implement keepalive for nginx > zeromq plugin that I have developed. > I have been inspired by ngx_http_upstream_keepalive_module. Was wondering > why nginx uses a kind of two linkedlist bas

Re: Nginx on Windows PHP fastcgi read timeouts

I found the cause on ever page i noticed it had Google Map's/Location running the person who wrote the Location addon in the component on Joomla for some reason thought it was good coding to wait for a link load. So the reason it time'd out is because it is connecting to a google maps link that nev

Re: $upstream_addr is returning blank

Thanks Valentin V. Bartenev !! I was using it before the line proxy_pass http://xyz.com After placing the code after proxy_pass, I am able to see the values.. Regards, Sunny Posted at Nginx Forum: http://forum.nginx.org/read.php?2,251039,251049#msg-251049

Re: Problem with big files

Hello! On Tue, Jun 17, 2014 at 06:51:10PM -0400, jakubp wrote: > Hi Justin > > Justin Dorfman Wrote: > --- > > > > > > I use a patch > > > Maxim provided some time ago allowing range requests to receive HTTP > > 206 if > > > a resource is not i

[PATCH] proposal to remove unused macro ngx_sleep()

Hello, ngx_sleep() is newer used ... and I guess it will newer used. ./os/unix/ngx_time.h:#define ngx_sleep(s) (void) sleep(s) Regards, yves Posted at Nginx Forum: http://forum.nginx.org/read.php?2,251044,251044#msg-251044 ___ nginx mailin

Re: Sticky equivalent

Am 18-06-2014 20:46, schrieb Stefanita Rares Dumitrescu: Oh god 1350$ Per year. It's cheap compared to some other commercial Servers, from my point of view. On 18/06/2014 16:49, Ruslan Ermilov wrote: On Wed, Jun 18, 2014 at 11:22:24AM -0300, Fabiano Furtado Pessoa Coelho wrote: Dear Rus

Re: $upstream_addr is returning blank

On Thursday 19 June 2014 03:00:44 tsunny wrote: > Hello, > > I want to access the value of $upstream_addr. Below is the code, > > location / { > > echo "up = $upstream_addr"; > > } > > > The response is just "up = " . What could be the reason for this? > The $upstream_addr variable keep

Re: upstream on OpenBSD not executing requests

On Thursday 19 June 2014 01:46:40 prkumar wrote: > I think you can not have two server directive in upstream, how nginx would > know which one to forward request to? > Will it do round robin? Not sure about that will have to check.. Can you try > by removing one.. > [..] You should read the docum

$upstream_addr is returning blank

Hello, I want to access the value of $upstream_addr. Below is the code, location / { echo "up = $upstream_addr"; } The response is just "up = " . What could be the reason for this? Posted at Nginx Forum: http://forum.nginx.org/read.php?2,251039,251039#msg-251039 ___