On 17/09/2010 19:47, Maxim Dounin wrote: > nside a server or location if block? > There is a good reason to disable anything but rewrite directives > in "if" blocks. I know about the 'if is evil' idea, but so long as you know what will happen (i.e. that if blocks don't behave like you might expect them to), is there any other inherent problem caused? Was the decision to not aby Eugaia - Nginx Mailing List - English
On 17/09/2010 17:27, Ryan Malayter wrote: > Is it possible to conditionally disable keep-alives via some sort of > configuration? I would suggest putting the keepalive_timeout directive inside an if block, but it's not permitted. Igor/Maxim : Is there a good reason why keepalive_timeout cannot be set inside a server or location if block? Cheers, Marcus. ________________________________by Eugaia - Nginx Mailing List - English
Hi, I've not had a detailed look at the config, but I think you're possibly suffering by having client_body_buffer_size 32m; Perhaps try something like : client_body_buffer_size 32k; or see how it works with the default (8k or 16k depending on the platform). Also, 25 worker processes is probably way too high. Try 1 per processor core, or possibly even fewer. You might also want to experiby Eugaia - Nginx Mailing List - English
Change 'permanent' to 'redirect'. Marcus. On 13/09/2010 18:39, ez77 wrote: >> In this configuration: >> >> rewrite ^(.*/)index.html http://$host$1 permanent; >> >> location / { >> index index.html; >> } >> >> nginx will not run the server level rewrite, after the internal > redrect, >> so there will not be the loop.In this configuratby Eugaia - Nginx Mailing List - English
Hi Roger, On 08/09/2010 22:40, Roger Hoover wrote: > Just curious, why create your own programming language? Well, I can see security issues related to just allowing unparsed/checked code being uploaded and run on the open-source website. Regardless, I'd want to put a parser in front of the underlying implementation (which is PHP). Since I was going to do that, I thought changing the synby Eugaia - Nginx Mailing List - English
Hi guys, I hope nobody minds me asking for help in this way. I'm asking for help from programmers to help set up a unique open-source project that could benefit a great many people. The Tagmata Project's three aims are : (1) to create a completely open-source website (2) to use the site to generate money (3) to use the profits to help alleviate poverty Full details of the whole project can bby Eugaia - Nginx Mailing List - English
Hi guys, I hope nobody minds me asking for help in this way. I'm asking for help from programmers to help set up a unique open-source project that could benefit a great many people. The Tagmata Project's three aims are : (1) to create a completely open-source website (2) to use the site to generate money (3) to use the profits to help alleviate poverty Full details of the whole project can bby Eugaia - Nginx Development
Hi, What might work just as well, and wouldn't suffer the API / performance issues would be making it easier to compile optional modules into the source without recompiling the whole Nginx source code. When I'm doing module development, I just build the object code of the module I'm writing, and combined it with the pre-compiled object files of all the other parts of Nginx, thereby typicallyby Eugaia - Nginx Mailing List - English
Hi, I don't know think there's a way of limiting the response size from proxied content, but there may be. Also, I just noticed the proxy_max_temp_file_size, which if you set to 0 disables using temporary files for proxying, so my previous comments about problems with large file sizes/streamed content can be ignored. Marcus. _______________________________________________ nginx mailing listby Eugaia - Nginx Mailing List - English
Hi, On 18/08/2010 22:31, hendrik wrote: > Hi everyone, > > I am using nginx as a proxy for custom URLs. I call URLs like > /proxy/www.example.com/favicon.ico and nginx acts as a proxy for > www.example.com/favicon.ico. This works fine as long as the response > from the upstream server is not a 301. If it is a 301, this gets > forwarded to the client which then calls the targetby Eugaia - Nginx Mailing List - English
> nginx adds the padding only for built-in error pages. > It does not add the padding for custom error pages by error_page or > error pages received from proxied, FastCGI, uWSGI, and SCGI servers. > Any reason why not? It makes sense to add it for others too, surely? Marcus. _______________________________________________ nginx mailing list nginx@nginx.org http://nginx.org/mailmby Eugaia - Nginx Mailing List - English
It's a 'feature' of Chrome, IE and probably some other browsers too. http://wiki.nginx.org/NginxHttpCoreModule#msie_padding If you're using version < 0.8.25, or msie_padding is set to 'off', then padding up to 512 bytes won't be done for Chrome when error pages are generated. Marcus. On 09/08/2010 22:39, Michael Shadle wrote: > You should submit a bug to chromium and give us the URL. Iby Eugaia - Nginx Mailing List - English
http://wiki.nginx.org/NginxHttpFcgiModule#fastcgi_param On 29/07/2010 17:18, Raina Gustafson wrote: > Issue: > I'd like to configure Magento to run in multi-domain mode. > I've been successful doing this via Apache in the past. > It seems that Nginx should be equally capable, but I haven't succeeded. > > Server Specs: > Nginx (latest) > PHP 5.3.3 > PHP-FPM enabled >by Eugaia - Nginx Mailing List - English
Hi, With a standard (i.e. no options) installation of 0.8.34 on my Linux machine I get a segfault if the resolver named in the conf file is a loopback address/IP, but the resolver does not exist. Other non-existing resolvers don't cause a problem (they just hang, and probably will time out), only loopback ones. The debug log is : 2010/03/21 04:07:30 4287#0: *3 http cl:-1 max:1048576 2010/by Eugaia - Nginx Mailing List - English
On 02/25/2010 05:09 AM, agentzh wrote: > On Sat, Feb 20, 2010 at 2:50 PM, Brian Long<brian@dotspots.com> wrote: > >> I might have just figured out the answer to my own question. It looks like >> setting v->no_cacheable = 0 is what was required. >> > Yeah, I believe that's what you need :) Please also test it in the > context of subrequests ;) >by Eugaia - Nginx Development
Markus Jelsma wrote: > Thank you for your quick answer, although it is not quite a satisfaction to > read it's not possible at the moment. > > How can i stay up to date for such a feature if it were to be implemented in > the - hopefully nearby - future? > > I have another question, is my current solution really much slower than doing > it all in one location directive?by Eugaia - Nginx Mailing List - English
> > Hi, > > The only option then for sticky sessions is ip_hash, not cookies. > No, it's also possible to direct traffic to particular backend servers using cookies too. In fact there are more ways of directing traffic to backends/clusters with Nginx than there are with HAProxy - in the sense of the number of ways of choosing a cluster (which could just be one server) - but AFAIKby Eugaia - Nginx Mailing List - English
Laurence Rowe wrote: > I would take a look at HAProxy which has better support for this use > case, allowing for requests to be retried against another server if > their associated backend is down. > I would agree that if you're just wanting to do proxying, then HAProxy is probably a better way to go, however the above is also possible in Nginx using upstreams. Marcus. _________by Eugaia - Nginx Mailing List - English
saltyflorida wrote: > saltyflorida Wrote: > ------------------------------------------------------- > >> Eugaia Wrote: >> -------------------------------------------------- >> ----- >> >>> saltyflorida wrote: >>> >>>> I forgot to mention that I am using caching >>>> >> with >> >&gby Eugaia - Nginx Mailing List - English
saltyflorida wrote: > I forgot to mention that I am using caching with the HTTP Proxy module and that I only want to cache responses from the production servers. When I have the cookie set to "testing" or "staging", I'd like to bypass the cache and talk directly to the backend. Does this sound feasible? > Sure. Do a rewrite using your $backend variable under the 'locaby Eugaia - Nginx Mailing List - English
Hi, merlin corey wrote: > Doesn't it make more sense to have production, static, and dev as > separate server blocks entirely with their own hostnames? This is, at > the least, traditional :). > Yes, I would agree with this (and it should perform a little better too). Marcus. _______________________________________________ nginx mailing list nginx@nginx.org http://nginx.org/mailby Eugaia - Nginx Mailing List - English
Hi, saltyflorida wrote: > Is it possible to switch backend clusters of servers based on a cookie? > > I would like to set a cookie named "env" and do something like this: > > if ($http_cookie ~* "env=testing(;|$)") { > proxy_pass http://backend_testing; > } > if ($http_cookie ~* "env=staging(;|$)") { >by Eugaia - Nginx Mailing List - English
Hi, tOmasEn wrote: > Maybe not many people using xslt as main web layout. but I do. > > This patch is similar to gzip_disable. xslt_enable only enable xslt > transform for certain user agent. > > e.g. > xslt_enable "Googlebot" > will only enable xslt transform output for google's crawler. > > And, I'm also planing some other improve on xslt module. Like:by Eugaia - Nginx Mailing List - English
Hi, arianna wrote: > want to store urls (locations) in files and issue redirects based on file contents. $request_body looks like it's only available on proxy... > The eval module is probably what you want here - http://github.com/vkholodkov/nginx-eval-module I would suggest storing the URLs in a memcached server rather than on file (or do both and check the file only if the memcacheby Eugaia - Nginx Mailing List - English
Hi, Laurence Rowe wrote: > Hi, > > I've got Nginx 0.7.64 running as a loadbalancer / transformation proxy > behind varnish. I'd like to use ip_hash so users get the benefit of > session affinity on my app servers. Though I seem to have > real_ip_header setup correctly ($remote_addr is correct as shown by > X-Real-IP on my app servers), all the requests end up using only a >by Eugaia - Nginx Mailing List - English
Hi, yomuppet wrote: > Hello, > > I have noticed that we seem to consistently get an nginx segault when reaching around 600 requests per second (reverse proxy). > > Here is the nginx build information: > $ nginx -V > nginx version: nginx/0.8.29 > built by gcc 4.1.2 20080704 (Red Hat 4.1.2-44) > TLS SNI support disabled > configure arguments: --add-module=../agentzh-chby Eugaia - Nginx Mailing List - English
Hi, Bob wrote: > Thanks for the response, greatly appreciated :) However I'm getting Unknown directive 'if' when trying to add this into my nginx config - any ideas? > Is your 'if' statement under a server or location block? If not, it won't work. http://wiki.nginx.org/NginxHttpRewriteModule#if Marcus. _______________________________________________ nginx mailing list nginx@nginx.orby Eugaia - Nginx Mailing List - English
Hi, Maxim Dounin wrote: >> >> The example is obviously correct, but it doesn't truly explain the >> reason for getting the 404 for accessing /users/xxx URLs (even >> though the result is almost the same). The reason is to do with the >> order that locations are handled, specifically that ^~ locations are >> handled before ~* and ~ ones, and if they match, thenby Eugaia - Nginx Mailing List - English
Hi, Maxim Dounin wrote: > Hello! > > On Sun, Jan 24, 2010 at 10:45:32PM +0100, Piotr Sikora wrote: > > >>> 2. Note "internal" in location /users/. It means "only visible >>> for internal redirects", so even user called "users" should be >>> correctly processed by the first location. >>> >> Actually,by Eugaia - Nginx Mailing List - English
Hi, I may be interested. I have a fair amount of experience with Nginx module development and would be available in the next couple of weeks. Please feel free to contact me at ngx (dot) eugaia (at) gmail (dot) com. Regards, Marcus Clyne.by Eugaia - Nginx Mailing List - English