On Fri, Feb 11, 2011 at 04:54:18AM -0500, chenxee wrote: > hi there, > > I'm new to nginx and trying to configure nginx and uwsgi to get > alias+seo url working, something like this: > > http://domain.com/shop/product/123 - /shop is an alias and shop dir > doesnt exist in filesystem under doc root, and this url trying to pass > query string as ?product=123 > > to gby Igor Sysoev - Nginx Mailing List - English
On Feb 10, 2011, at 23:45 , MAXTEXAHN wrote: > а я его вот так перезапускаю правельно? > > killall -HUP nginx > =)))) Нет, неправИльно. Сигнал нужно посылать только главному процессу: http://sysoev.ru/nginx/docs/control.html -- Игорь Сысоев http://sysoev.ru _________________________by Igor Sysoev - Nginx Mailing List - Russian
On Thu, Feb 10, 2011 at 06:04:41PM -0600, Michael Lustfield wrote: > Recently I noticed that logrotate does not actually rotate the files correctly. > I noticed this in 0.8.54. > > The issue seems to be that neither -USR1 or -s reopen will reopen the log files > after they've been rotated. I'm not sure if this specific to the version > packaged in Debian but I've seen it as an iby Igor Sysoev - Nginx Development
On Thu, Feb 10, 2011 at 10:19:39PM -0500, Sirsiwal, Umesh wrote: > This path extends existing resolver command to optionally take a second parameter. The second parameter can be used to override default port 53. Thank you for the patch, but a port should be set as "host:port", but not as second parameter. -- Igor Sysoev http://sysoev.ru/en/ _______________________________________by Igor Sysoev - Nginx Development
On Thu, Feb 10, 2011 at 07:05:57PM -0800, Naoki Hiroshima wrote: > Hi, > > The workaround for safari/keep-alive issue being introduced by 0.8.33 > seems to be way too aggressive. Since it's a POST issue, we should > unwillingly disable keep-alive only when it's POST. Please read this: https://bugs.webkit.org/show_bug.cgi?id=5760 The problem is that keepalive should be disable befoby Igor Sysoev - Nginx Development
On Feb 10, 2011, at 23:27 , MAXTEXAHN wrote: >> # nginx -t >> : unexpected end of file, expecting ";" or "}" in >> /usr/local/etc/apache22/mime.types:1237 >> configuration file /usr/local/etc/nginx/nginx.conf >> test failed > и > # nginx -t > : unknown directive "format" in > /usr/local/etc/nginx/nginx.conf:29 > configuraby Igor Sysoev - Nginx Mailing List - Russian
On Feb 10, 2011, at 23:24 , MAXTEXAHN wrote: > Igor Sysoev Пишет: > ------------------------------------------------------- >> On Feb 10, 2011, at 17:36 , MAXTEXAHN wrote: >> >>> почему именно этот, второй >> домен >>> распространяться на >> правило: >>> >>> server { >&gby Igor Sysoev - Nginx Mailing List - Russian
On Feb 10, 2011, at 23:06 , Igor Sysoev wrote: > On Thu, Feb 10, 2011 at 11:25:23AM -0500, thoseg wrote: >> And of course, I made a mistake with the example link provided... I >> should have written : >> >> $prefix/$hash/$timestamp/$path/to/file.mp4 > > In 0.8.51+ you can try new ngx_http_secure_link_module functionality: > > /dir/MD5_HASH/TIMESTAMP/patby Igor Sysoev - Nginx Mailing List - English
On Thu, Feb 10, 2011 at 11:25:23AM -0500, thoseg wrote: > And of course, I made a mistake with the example link provided... I > should have written : > > $prefix/$hash/$timestamp/$path/to/file.mp4 In 0.8.51+ you can try new ngx_http_secure_link_module functionality: /dir/MD5_HASH/TIMESTAMP/path/to/file.mp4 location /dir/ { location ~ ^/dir/(?<HASH>[\w\-by Igor Sysoev - Nginx Mailing List - English
On Feb 10, 2011, at 22:07 , grigory wrote: > У меня отдаётся с сервера куча статики. > Но появилось штук 30 файлов, которые > трафика на 150 Мбит/с "кушают", посему я > решил переместить их на "дружественные" > файл-хостинги,by Igor Sysoev - Nginx Mailing List - Russian
On Feb 10, 2011, at 19:40 , Parker, Joshua wrote: > Thanks everyone. My issue has been resolved, but now I have a new issue and its with emails. This is the bounce back I get: > > Delivery to the following recipient failed permanently: > > mailman-request@mulyoo.org > > Technical details of permanent failure: > Google tried to deliver your message, but it was rejectby Igor Sysoev - Nginx Mailing List - English
On Feb 10, 2011, at 20:54 , Francis Daly wrote: > On Thu, Feb 10, 2011 at 11:40:07AM -0500, Parker, Joshua wrote: > > Hi there, > >> Thanks everyone. My issue has been resolved, but now I have a new issue and >> its with emails. This is the bounce back I get: > > Point your web browser at http://mulyoo.org:8000/ Click the "mailman" > link. You're talkby Igor Sysoev - Nginx Mailing List - English
On Feb 10, 2011, at 19:03 , Matthias-Christian Ott wrote: > On Thu, Feb 10, 2011 at 06:56:50PM +0300, Igor Sysoev wrote: >> On Thu, Feb 10, 2011 at 04:36:03PM +0100, Matthias-Christian Ott wrote: >>> On Thu, Feb 10, 2011 at 06:24:31PM +0300, Igor Sysoev wrote: >>>> On Feb 10, 2011, at 18:04 , Matthias-Christian Ott wrote: >>>>> >>>>> Whby Igor Sysoev - Nginx Development
On Thu, Feb 10, 2011 at 04:36:03PM +0100, Matthias-Christian Ott wrote: > On Thu, Feb 10, 2011 at 06:24:31PM +0300, Igor Sysoev wrote: > > On Feb 10, 2011, at 18:04 , Matthias-Christian Ott wrote: > > > > > > What I mean was the following > > > > > > server { > > > location /a { > > > ssl_client_certificate a/ca.pem; > &by Igor Sysoev - Nginx Development
On Feb 10, 2011, at 18:31 , Parker, Joshua wrote: > Hello everyone. I am having a little issue with mailman. I've installed and configured mailman for mulyoo.net which works. On this particular server the software is Ubuntu 10 (Lucid). On a different server, I did the same installation and configuration, but this server is running Ubuntu 8 (Hardy). However, when I visit this server (mulyoo.orgby Igor Sysoev - Nginx Mailing List - English
On Feb 10, 2011, at 18:04 , Matthias-Christian Ott wrote: > > What I mean was the following > > server { > location /a { > ssl_client_certificate a/ca.pem; > ssl_crl a/a.crl; > } > > location /b { > ssl_client_certificate b/ca.pem; > ssl_crl a/a.crl; > } > } > > As far as I can tell from the documentation,by Igor Sysoev - Nginx Development
On Feb 10, 2011, at 17:36 , MAXTEXAHN wrote: > почему именно этот, второй домен > распространяться на правило: > > server { > listen 80; > server_name _; > > location / { > deny all; > } > } > Что показывает "nginx -t" ? -- Igor Sysoev http://sysoev.ru/en/ __by Igor Sysoev - Nginx Mailing List - Russian
On Feb 10, 2011, at 10:36 , Matthias-Christian Ott wrote: > Hi, > > at the moment it is only possible to set variables for SSL client > verification in the http oder server context. I would be useful to have > them at least in location, so that one could verify the certificate > according to the requested directory. Would this be possible? These are not variables, but directiby Igor Sysoev - Nginx Development
On Feb 10, 2011, at 15:04 , skolodez wrote: > Пытаюсь собрать последний nginx в > 64-битном варианте под Solaris 10 u8/9. > Все нужные библиотеки уже собраны с > нужными параметрами и установлены, в > 64-битном варианте, в нестандартную > паby Igor Sysoev - Nginx Mailing List - Russian
On Wed, Feb 09, 2011 at 01:37:02PM -0500, MAXTEXAHN wrote: > nginx/0.7.67 + apache 2.2 > > server { > listen 80; > server_name xxx.domain1.ru xxx.domain2.ru; > > access_log /www/xxx/nginx_access.log; > error_log /www/xxx/nginx_error.log; > > location / { > location > ~*^.+\.(jpg|jpeg|gif|ico|css|zip|tgz|gz|rar|bz2|doc|xlby Igor Sysoev - Nginx Mailing List - Russian
On Wed, Feb 09, 2011 at 03:09:08PM +0100, rainer@ultra-secure.de wrote: > > On Wed, Feb 09, 2011 at 02:54:21PM +0100, rainer@ultra-secure.de wrote: > > > >> I want to put NGINX in front of a server that requires > >> client-certificates. > >> I need to pass the certificate to the upstream. > >> > >> How does one do that? > >> > &by Igor Sysoev - Nginx Mailing List - English
On Wed, Feb 09, 2011 at 02:54:21PM +0100, rainer@ultra-secure.de wrote: > I want to put NGINX in front of a server that requires client-certificates. > I need to pass the certificate to the upstream. > > How does one do that? > > The upstream is a native jboss server (EJBCA in fact). You can pass client certificate using some header, X-SSL-CERT, for example: proxy_set_headerby Igor Sysoev - Nginx Mailing List - English
On Wed, Feb 09, 2011 at 11:50:50AM +0100, vicosoft@gmail.com wrote: > Imap works reverse proxy on port 143 successfully. With this setting. > > File -> mailauth.pm: > > package mailauth; > use nginx; > > sub handler { > my $r = shift; > $r->header_out("Auth-Status", "OK"); > $r->header_out("Auth-Server", '172.18by Igor Sysoev - Nginx Mailing List - English
On Tue, Feb 08, 2011 at 08:14:49PM +0530, Sparsh Gupta wrote: > Hello > > I was using Pound for negotiating ssl but recently someone told me > that nginx https module is quite better. I have setup nginx 0.8.54 on > my ubuntu 10.10 64bit, and did a basic setup of ssl but dont > experience a very good latency. > > Is there a document on tips and best practices, I should foby Igor Sysoev - Nginx Mailing List - English
On Tue, Feb 08, 2011 at 01:24:38PM +0000, António P. P. Almeida wrote: > On 8 Fev 2011 13h11 WET, igor@sysoev.ru wrote: > > > On Tue, Feb 08, 2011 at 11:55:27AM +0100, Gregory Agerba wrote: > > > >> Thanks Antonio, now that worked. > > > > You should think not in negative way: > > > > if ($request_uri !~* "^/documents/(?:[A... ") { {by Igor Sysoev - Nginx Mailing List - English
On Tue, Feb 08, 2011 at 02:20:00PM +0100, Gregory Agerba wrote: > Hi Igor, > > Yes, but my rule is only acting as a simple *Access Control List* which > expect a very special pattern to match and anything else should be discarded > with an error message/page. > > The given pattern is not accessed directly by users, it’s an application > that send requests to that givenby Igor Sysoev - Nginx Mailing List - English
On Tue, Feb 08, 2011 at 11:55:27AM +0100, Gregory Agerba wrote: > Thanks Antonio, now that worked. You should think not in negative way: if ($request_uri !~* "^/documents/(?:{36})/pages/(?:{36})/items/(?:{36}" -- Igor Sysoev http://sysoev.ru/en/ _______________________________________________ nginx mailing list nginx@nginx.org http://nginx.org/mailman/listinfo/nginxby Igor Sysoev - Nginx Mailing List - English
On Fri, Feb 04, 2011 at 06:23:18AM -0500, Craken wrote: > Да, вот последние строчки: > > > checking for int size > > objs/autotest.c:1: error: CPU you selected does not support x86-64 > instruction set Убрать --with-cpu-opt=pentium4 -- Игорь Сысоев http://sysoev.ru _______________________________________________ nginx-ru mailing lby Igor Sysoev - Nginx Mailing List - Russian
On Thu, Feb 03, 2011 at 08:06:14PM +0100, Paul Bergstrom wrote: > I want to install nginx with support for ssl. I know how to do that. > > --with-http_ssl_module --with-openssl=/... > > > I'm uncertain what path I should use for the last argument. > > I have openssl installed on Debian. which openssl gives > /usr/bin/openssl. Is this the path I should enter? > &by Igor Sysoev - Nginx Mailing List - English
On Thu, Feb 03, 2011 at 05:43:50AM -0500, xopek wrote: > > Это неправильная > > конфигурация, вот > > правильная: > > > > location / { > > try_files $uri $uri/ @maxsite; > > } > > > > location ~ \.php { > > fastcgi_pass unix:/tmp/php-fpm.sock; > &by Igor Sysoev - Nginx Mailing List - Russian
![]() |
![]() |
![]() |
![]() |
|