hm, still "hot"... no idea anyone? btw.: just wondering if these messages are even "readable" as none of the appear on the mailing list...by revirii - Nginx Mailing List - English
hmm... no one has an idea? btw: strange, this topic doesn't appear on the nginx mailing listby revirii - Nginx Mailing List - English
Hi, just a question... is there some sort of internal nginx DNS cache? I have a strange problem here... basic scenario: i have multiple domains (like vhost 1) with different domains (my.domain.com, www.domainx.com etc., just example names). But all of them proxy_pass to the same intermediate vhost (vhost 2), which then sends the requests to the backends. A resolver.conf is used, using the provby revirii - Nginx Mailing List - English
Hi, thanks for your answer :-) > It's an implementation detail. As of now, two identical > upstream{} blocks will map the same ip address to the same peer's > number. But it's not something guaranteed. ok, this is the behaviour when the upstreams are identical, i.e. they have the same backends. That would be ok for me. But what if the backends are not identical? My exampby revirii - Nginx Mailing List - English
hmm... no one? Is this unknown or a secret? At least i wasn't able to find any detailed documentation about this.by revirii - Nginx Mailing List - English
Hello, i have 2 upstreams, each with 3 backend servers, where backendA is the same backend in both upstreams. upstream one { server backendA; server backendB; server backendC; } upstream two { server backendA; server backendD; server backendE; } A user with his IP sends a request, gets passed to upstream one and is sent to backendA. Shortly after that heby revirii - Nginx Mailing List - English
Good Morning, > If it connects *to* 127.0.0.1, it will connect *from* 127.0.0.1 (which > is one of the nginx server's addresses). > > If it connects *to* 192.168.0.1, it will connect *from* 192.168.0.1 > (which is one of the nginx server's addresses). Hm, the said nginx vhost doesn't use 127.0.0.1 or a lan address in combination with port 80 - varnish listens on *.80. theby revirii - Nginx Mailing List - English
Good Morning, > You can see the right X-Forwarded-For header with tcpdump. > > Take a look at the log format varnish uses. I don't know how to > configure varnish, but with Apache you have to change your LogFormat > from > > LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" > \"%{User-Agent}i\"" combined >by revirii - Nginx Mailing List - English
Hey, thx for the fast answer :-) > The connection to varnish comes from the address 127.0.0.1. That's > what it logs here. > The connection to varnish comes from the address 192.168.0.1. That's > what it logs here. But why? The only difference is the proxy_pass statement: proxy_pass http://127.0.0.1:80; vs. proxy_pass http://192.168.0.1:80; No other changes were dby revirii - Nginx Mailing List - English
Hey, maybe the solution is really simple, but i can't find it. nginx (1.2.1) handles ssl and proxies the traffic to the backend (varnish, which also handles http): location / { proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://127.0.0.1:80; } The rby revirii - Nginx Mailing List - English
Hello, i have a load balancing setup running with nginx in front and 2 tomcats as backend: upstream backend { ip_hash; server 192.168.1.100; server 192.168.1.101; } Runs fine so far, but from time to time one of the tomcats crashes and needs to be restarted. As soon as nginx notices that the tomcat is coming up, nginx starts to forward requests to the starting-up tomcat. But itby revirii - Nginx Mailing List - English
hmmm... as no one answered and i couldn't find any further informations on the web, i have to assume nginx isn't able to handle the above scenario. What a pity.by revirii - How to...
Hi, we have a domain example.com, and several subdomains. For https we have a wildcard certificate for *.example.com. I've tried the following: vhostA: server { listen 1.2.3.4:443; server_name a.example.com; ... } vhostB: server { listen 1.2.3.4:443; server_name b.example.com; ... } (Possibly there will be more vhosts with htby revirii - How to...
Hi, we want to establish some service that will deliver static files (images) with a size between 1-120 KB. The service should handle (at the moment) ~130.000.000 requests per month, so not that few and not extremly many requests. The to-be-served files have a size of several hundred GBs in total. Some of the files (5-10%) are asked more frequently and the bigger part less frequently. Let'sby revirii - Nginx Mailing List - English
revirii Wrote: ------------------------------------------------------- > Igor Sysoev Wrote: > -------------------------------------------------- > Hm, what is \d{2}? Is there any documentation? hm, shame on my head. It's for digit characters. I should work more with regular expressions...by revirii - Nginx Mailing List - English
Igor Sysoev Wrote: ------------------------------------------------------- > You DO need the locations, but you DO NOT need the > rewrites. ok. > Why do you use space in "([0-9] {2}" ? Because space was used here: http://wiki.nginx.org/NginxHttpRewriteModule#rewrite > Here is example for 2 numbers location: > > # 2 numbers > location ~ ^/by revirii - Nginx Mailing List - English
I've simplified the last rule a bit, to see where the problem might be. rewrite "^/img/default/([0-9] {3})([0-9] {3})/(.*)\.(gif|jpg|jpeg|png|tiff|bmp)$" http://www.google.com break; -> rewrite "^/img/default/(.*)/(.*)\.(gif|jpg|jpeg|png|tiff|bmp)$" http://www.google.com break; So i replaced (-?[0-9] {3})(-?[0-9] {3})(-?[0-9]+) with (.*), and now the rule works.by revirii - Nginx Mailing List - English
Greetings, i'm currently facing a problem with some rewrites. Given an url i have to rewrite it to a local folder. url: www.domain.com/img/default/420006675369688559/image.png doc root: /home/images/public/ local path (under doc root): 420/006/420006675369688559/default.png So the rewrite rule should take the number and split it, taking the 1st (420) and 2nd (006) three numbers out of tby revirii - Nginx Mailing List - English
Igor Sysoev Wrote: ------------------------------------------------------- > BTW, why do you prefer to use varnish instead of > nginx built-in cache ? Well... we needed to do caching fast, and a co-worker is quite good in varnish issues. It would've taken longer to test how this (incl. cookie & session handling) is done in nginx. But maybe, when there's some time... :-)by revirii - Nginx Mailing List - English
that's it - thx a lot :-)by revirii - Nginx Mailing List - English
Hello, we have a little problem with, as the topic says, "Nginx+varnish & delivered error_page". We have nginx in front as proxy, behind there's a varnish cashing stuff from a tomcat backend. Sometimes the tomcat crashes and delivers 503 to varnish; varnish sends 503 to nginx, nginx sends it to the client (browser, fiddler, ...). I've created some 50x error page which is deliveby revirii - Nginx Mailing List - English