On 2013-02-22 23:05, Valentin V. Bartenev wrote: > IMHO, > > location ~ ^(?<script_name>.+\.php)(?<path_info>/.*)?$ { > > looks better. In order to put yet another iteration into the game, I prefer the script_name part to be non-greedy location ~ ^(?<script_name>.+?\.php)(?<path_info>/.*)?$ { Of course it still depends on someone's preference whby csg - Nginx Mailing List - English
On 2012-11-28 15:05, Valentin V. Bartenev wrote: > On Wednesday 28 November 2012 16:14:16 Maxim Dounin wrote: [...] >> There is more than one patch(1) implementations floating around, >> and I wouldn't be surprised fuzz in one of them will be reject in >> another one. > > Ok, you're right, I haven't been thought that this time the problem > is so serious. > > Thby csg - Nginx Mailing List - English
On 2012-11-27 23:32, Valentin V. Bartenev wrote: > Don't worry, it's indeed minor adjustments while applying. > It should work as well as with the previous nginx version. Great, thanks for confirmation. If anyone is interested for reasons of convenience, I applied the patch to nginx 1.3.9, resolved the rejects and did a fresh unified diff. https://www.schug.net/dist/nginx/patch.spdy-53-by csg - Nginx Mailing List - English
On 2012-11-27 15:26, Maxim Dounin wrote: > Changes with nginx 1.3.9 27 > Nov 2012 [...] Thanks :) Will there be an updated version of the SPDY patch as well? It looks like patch.spdy-53.txt just needs minor adjustments in src/http/ngx_http.h and src/http/ngx_http_request_body.c (at least it applies, compiles and runs in my case after doing so) butby csg - Nginx Mailing List - English
On 2012-09-26 19:03, adamchal wrote: > Anybody having issues with the echo_location (and > echo_location_async) > directive? I have tried to get this to work with v1.1.18 and v1.3.6, > and > they both exhibit the same behavior. Basically, only the output from > the > /main block is echo'd out. > > My nginx config (basically a copy-and-paste) from the echo module's &by csg - Nginx Mailing List - English
On 2012-09-25 03:47, Listjj wrote: > May i ask where can i download the source of ngx_lua? Speaking of lua-nginx-module, it's hosted on GitHub https://github.com/chaoslawful/lua-nginx-module https://github.com/chaoslawful/lua-nginx-module/tags _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby csg - Nginx Mailing List - English
On 2012-08-29 13:11, ShreyasPrakash wrote: > Can't we get this functionality without using lua-nginx-module? AFAIK Nginx does support this out of the box, i.e. there's nothing like the internal functions tolower/toupper of RewriteMap in Apache HTTP (see http://httpd.apache.org/docs/2.4/mod/mod_rewrite.html#rewritemap). If you prefer Perl over Lua, go with the Perl module. _________________by csg - Nginx Mailing List - English
On 2012-08-28 11:30, ShreyasPrakash wrote: > Hi, > > I would like to know how to convert the URLs to lowercase. When > somebody > hits an URL ( irrespective of the case ), it should be converted to > lowercase in the address bar. With the help of lua-nginx-module (see https://github.com/chaoslawful/lua-nginx-module) it could look like this ... location ~ "\p{Lu}" {by csg - Nginx Mailing List - English
On 2012-08-02 07:39, Christoph Schug wrote: > Given is following minimized test case > > server { > listen 80; > server_name t1.example.com; > > root /data/web/t1.example.com/htdoc; > > location ~ ^/quux(/.*)?$ { > alias /data/wby csg - Nginx Mailing List - English
On 2012-08-02 12:42, Maxim Dounin wrote: [...] > And this is why it's not recommended to use enumerated captures > except for very simple configurations (or "rewrite" directive, > where use of enumerated captures immediatly follows regexp > matching). Use named captures instead and you'll be fine. Thanks Maxim, using named captures it exactly what I did. The question to meby csg - Nginx Mailing List - English
On 2012-08-02 12:01, Maxim Dounin wrote: [...] > I tend to think that it's more or less clarified here: > > http://www.fastcgi.com/om_archive/kit/doc/fcgi-spec.html#S6.2 > > As params are expected to represent "CGI/1.1 environment > variables", keys should be unique. I somehow missed that part, thanks for the hint. [...] > I'm don't think we want to require uniquenby csg - Nginx Mailing List - English
Hello! I have another interesting scenario ;-) Given is following minimized test case server { listen 80; server_name t2.example.com; root /data/web/t2.example.com/htdoc; location ~ ^/bar(/.*)? { alias /data/web/t2.example.com/htdoc/foo$1;by csg - Nginx Mailing List - English
On 2012-08-02 04:32, jakecattrall wrote: > Hey folks, > > I'd like to turn your attentions to this frustrating issue I've been > facing. > > I'm running a dedicated server... Centos 6, PHP 5.3.3, Nginx 1.0.15. > Great hardware, no problems. > > Nginx uses fastcgi to run php. > > The server communicates with another server using remote sql. > > A file called dby csg - Nginx Mailing List - English
Most of the times when configuring a FastCGI application it is just good enough to include the fastcgi.conf which ships with the Nginx distribution. On the other hand sometimes it is required to just change one or few of the definitions in that file, for example when the application resided outside document root. Practically something like include fastcgi.conf; fastcgi_paramby csg - Nginx Mailing List - English
Hello! Given is following minimized test case server { listen 80; server_name t1.example.com; root /data/web/t1.example.com/htdoc; location ~ ^/quux(/.*)?$ { alias /data/web/t1.example.com/htdoc$1; try_files '' =404; }by csg - Nginx Mailing List - English
Most IPv6 stuff was introduced with newer versions of the GeoIP library (IIRC something around 1.4.7), so you might either want to autodetect GeoIP's capabilities or embed the relevant stuff into #if LIBGEOIP_VERSION >= 1004007 ... #endif directives. Otherwise you might break builds against older versions of the library.by csg - Nginx Mailing List - English
Hi Maxim and Igor! in the meantime we served around 15 million requests successfully without any issue on production. As a long term fix would it be possible for get Maxims' patch merged into to the official code base. As this is a change in behavior I would understand if it doesn't get merged into the stable branch, but merging this into the development branch would be excellent. # HG changby csg - Nginx Mailing List - English
I can confirm that the patch fixes the issue on my test setup :-) Will add it to my Nginx package and deploy it on production. Many thanks Maxim for your fantastic support on this issue (and all the work you do on this amazing and very helpful list)!by csg - Nginx Mailing List - English
Ah sorry, just saw your patch ... will give that a try! Many thanks :-)by csg - Nginx Mailing List - English
Here as a follow up the debug output plus additional information: # nginx -V nginx: nginx version: nginx/1.0.6 nginx: configure arguments: --with-debug --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --sbin-path=/usr/sbin/nginx --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --pid-path=/var/run/nginx.pid --user=nginx --group=nginx --with-http_geby csg - Nginx Mailing List - English
Maxim Dounin Wrote: ------------------------------------------------------- Hello again! > .... and $backend won't be set as a result. > Moving "set" before > "rewrite .. break" will do the trick. Right, in this case the $backend applies to proxy_pass and the request gets proxied but unfortunatelly in this case the rewrite rule does not have effect anymoreby csg - Nginx Mailing List - English
Maxim Dounin Wrote: ------------------------------------------------------- > Errors suggest you don't have $backend set, and > resulting > proxy_pass tries to go to "http://" which is > invalid. Yup, I am just curious how to accomplish that if you want to perform some rewriting before, for example to strip off some leading parts of the URL path. I came up with folloby csg - Nginx Mailing List - English
Maxim Dounin Wrote: ------------------------------------------------------- > Resolver is only used for proxy_pass with > variables, i.e. > something like > > resolver 127.0.0.1; > set $backend "foo.example.com"; > proxy_pass http://$backend; > > In such setup ip address of "foo.example.com" will > be looked up > dynaby csg - Nginx Mailing List - English
I have a short question on Nginx's proxy module. In our setup we reverse proxy specific requests to the server of an external partner via proxy_pass. Over the weekend the partner updated DNS but Nginx wasn't catching up the change and still sent traffic to the old server despite the fact the TTL of the record was little enough. An additional obstacle might be that in our case we have for examplby csg - Nginx Mailing List - English
It just depends what you consider a large configuration. For example we have a bunch of Ngnix instances running each with roughly 200,000 lines of configuration, although taking just the raw number of lines as such might be a bad metric.by csg - Nginx Mailing List - English
agentzh Wrote: ------------------------------------------------------- > On Tue, May 31, 2011 at 11:50 PM, Piotr Sikora > <piotr.sikora@frickle.com> wrote: > There's a specification for the RDS binary format > in ngx_drizzle's README file: > > http://github.com/chaoslawful/drizzle-nginx-module > > See the Output section there. First of all, thanks tby csg - Nginx Mailing List - English
Igor Sysoev Wrote: ------------------------------------------------------- > If perfomance is the key, you should use a file > system. > Or you believe that reading from MySQL is magic > zero transportation ? :) For sure not, and I didn't say so. But instead of bringing yet another software component into play and entering a semi-flameware about the pros and cons to store blobsby csg - Nginx Mailing List - English
mow Wrote: ------------------------------------------------------- > You may try "fuse" (http://fuse.sourceforge.net/), > implement a tiny file > system easily which uses mysql as data source and > acts as a real file > system. Correct me if I am wrong, but I reckon that context switches between kernel and a userland filesystem would be detrimental to the perforby csg - Nginx Mailing List - English
SplitIce Wrote: ------------------------------------------------------- > The largest > disadvantage is the size of the table. This can be easily avoided by sharding the data into many tables, accessing it per modulo operation on the numerical key. > Oh and JSON > can be binary safe if > implmented correctly with correct escape > sequences, yes? But this would requby csg - Nginx Mailing List - English
Igor Sysoev Wrote: ------------------------------------------------------- > I can not say anuthing about subject, I'm just > interesting are any > advanatges to store images in MySQL instead of > file system ? First of all quite a lot of backend processes and application code relies on it. Those interfaces cannot be changed easily. But on the other hand for the ease of handby csg - Nginx Mailing List - English