<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
alguien habla castellano??<div><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">hello</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">,</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">which is the</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">number of processes to</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">host a site</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">in</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">nginx</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">?</span></div><div><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">You can</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">have a server</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">on site,</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">which serves to</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps atn" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">re-</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">send requests</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">within the</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">local</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); "> </span><span class="hps" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">network</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">?</span><span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 16px; background-color: rgb(245, 245, 245); ">?</span><font color="#333333" face="arial, sans-serif" size="3"><br></font><br><div><div id="SkyDrivePlaceholder"></div>> From: nginx-request@nginx.org<br>> Subject: nginx Digest, Vol 27, Issue 33<br>> To: nginx@nginx.org<br>> Date: Fri, 13 Jan 2012 13:57:52 +0000<br>> <br>> Send nginx mailing list submissions to<br>> nginx@nginx.org<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://mailman.nginx.org/mailman/listinfo/nginx<br>> or, via email, send a message with subject or body 'help' to<br>> nginx-request@nginx.org<br>> <br>> You can reach the person managing the list at<br>> nginx-owner@nginx.org<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of nginx digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: alias, regex and try_files am i doing it wrong, or is<br>> this a bug? (Maxim Dounin)<br>> 2. Re: mod_aclr2 (Martin Loy)<br>> 3. Re: [PATCH 2 of 2] add support for setting worker processes<br>> and CPU affinity automatically (Joshua Zhu)<br>> 4. Re: [PATCH 2 of 2] add support for setting worker processes<br>> and CPU affinity automatically (Maxim Konovalov)<br>> 5. Limit robots (double)<br>> 6. help with replacing chars "_" to "." in a $variable (andres-m77)<br>> 7. Re: Limit robots (Ant?nio P. P. Almeida)<br>> 8. Re: Programmatic access to Nginx fcgi/proxy cache? (Martin Loy)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Fri, 13 Jan 2012 16:52:18 +0400<br>> From: Maxim Dounin <mdounin@mdounin.ru><br>> To: nginx@nginx.org<br>> Subject: Re: alias, regex and try_files am i doing it wrong, or is<br>> this a bug?<br>> Message-ID: <20120113125218.GC67687@mdounin.ru><br>> Content-Type: text/plain; charset=us-ascii<br>> <br>> Hello!<br>> <br>> On Thu, Jan 12, 2012 at 11:36:41PM -0500, takigama wrote:<br>> <br>> > Ok, i was trying to do drupal as a subdirectory on my site, but i've hit<br>> > a problem and I think its a bug. Im using 10.04 ubuntu, the nginx ppa<br>> > with 1.0.11 nginx. <br>> > <br>> > If i have the following config's and i try to retrieve the file<br>> > http://mysite/drupal/somefile:<br>> > <br>> > location ~ /drupal(.*) {<br>> > index index.php;<br>> > alias /local_config/$1;<br>> > try_files $uri @drupalrewrite;<br>> > }<br>> > <br>> > The file nginx is apparently trying retrieve<br>> > "/local_config//somefile/drupal/somefile" rather then<br>> > "/local_config//somefile", which leads me to believe $uri isnt being set<br>> > correctly by nginx.<br>> <br>> Yes, this looks like a bug for me.<br>> <br>> (Internally, the problem is a bit complex, and I event tend to <br>> think that behaviour of try_files with alias in a regexp location <br>> is inherently undefined, but the example above should certainly <br>> work as expected.)<br>> <br>> > If instead, i have this as a config:<br>> > <br>> > location /drupal/ {<br>> > index index.php;<br>> > alias /local_config/;<br>> > try_files $uri @drupalrewrite;<br>> > }<br>> > <br>> > it does the right thing, and try files will attempt to get<br>> > "/local_config/somefile", so im really confused as to why it happens.<br>> <br>> This works as expected.<br>> <br>> The difference is that in a regexp location the "alias" directive <br>> specifies full path to a file to use, and try_files isn't <br>> currently able to handle this.<br>> <br>> Maxim Dounin<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Fri, 13 Jan 2012 10:55:00 -0200<br>> From: Martin Loy <martinloy.uy@gmail.com><br>> To: nginx@nginx.org<br>> Subject: Re: mod_aclr2<br>> Message-ID:<br>> <CAHbGeW7vqP1_yK-y6CqKJzcE94BUhS8mORr1kgoyj2peESZrUQ@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Andrey<br>> <br>> thanks for your response and great nice work!!<br>> <br>> Regards<br>> <br>> M<br>> <br>> On Wed, Jan 11, 2012 at 4:09 PM, Andrey Belov <defan@nginx.com> wrote:<br>> <br>> > Martin,<br>> ><br>> > On Jan 11, 2012, at 7:31 PM, Martin Loy wrote:<br>> ><br>> > Would you explain the main difference between using your module and using<br>> > nginx as a reverse proxy and caching static content ?<br>> ><br>> ><br>> > In some situations, mod_aclr2 helps to avoid excessive disk I/O,<br>> > especially for big static responses.<br>> ><br>> > When nginx is used as a local reverse proxy and proxy_buffering is<br>> > enabled, every upstream reponse which can not fit into proxy buffers<br>> > may be temporarily saved on disk:<br>> ><br>> > http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffering<br>> > http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_temp_path<br>> ><br>> > For example, we have to process the request for 700mb video file,<br>> > without mod_aclr2:<br>> ><br>> > 1) nginx sends the request to apache<br>> > 2) apache sends 700mb file back to nginx<br>> > 3) nginx saves received file on disk (proxy_temp_path) and<br>> > starts sending it back to the client<br>> ><br>> > and with mod_aclr2:<br>> ><br>> > 1) nginx sends the request to apache<br>> > 2) apache sends a few bytes header with X-Accel-Redirect back to nginx<br>> > 3) nginx starts sending the file directly from disk<br>> ><br>> > You save your time and your disk at step #2.<br>> ><br>> > Of course, you also may use proxy_cache along with mod_aclr2,<br>> > but if your disks are fast enough, probably you won't need<br>> > to do any caching at all.<br>> ><br>> > Hope this helps.<br>> ><br>> ><br>> ><br>> > Regards<br>> ><br>> > M<br>> ><br>> > On Wed, Jan 11, 2012 at 11:54 AM, Ant?nio P. P. Almeida <appa@perusio.net>wrote:<br>> ><br>> >> On 11 Jan 2012 13h17 WET, defan@nginx.com wrote:<br>> >><br>> >> > Hello!<br>> >> ><br>> >> > Ever wondered how to set up NGINX as a local proxy for Apache 2.x<br>> >> > with minimum efforts?<br>> >><br>> >> Nice work Andrey. Opens up Nginx as a possibility for shared hosting<br>> >> (keep using .htaccess) and voids any resistance people might have trying<br>> >> Nginx out. It's sooo easy now :)<br>> >><br>> >> Thanks,<br>> >> --- appa<br>> >><br>> >> _______________________________________________<br>> >> nginx mailing list<br>> >> nginx@nginx.org<br>> >> http://mailman.nginx.org/mailman/listinfo/nginx<br>> >><br>> ><br>> ><br>> ><br>> > --<br>> > *Nunca hubo un amigo que hiciese un favor a un enano, ni un enemigo que<br>> > le hiciese un mal, que no se viese recompensado por entero.*<br>> > _______________________________________________<br>> > nginx mailing list<br>> > nginx@nginx.org<br>> > http://mailman.nginx.org/mailman/listinfo/nginx<br>> ><br>> ><br>> ><br>> > _______________________________________________<br>> > nginx mailing list<br>> > nginx@nginx.org<br>> > http://mailman.nginx.org/mailman/listinfo/nginx<br>> ><br>> <br>> <br>> <br>> -- <br>> *Nunca hubo un amigo que hiciese un favor a un enano, ni un enemigo que le<br>> hiciese un mal, que no se viese recompensado por entero.*<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20120113/615c8118/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Fri, 13 Jan 2012 21:08:25 +0800<br>> From: Joshua Zhu <zhuzhaoyuan@gmail.com><br>> To: nginx@nginx.org<br>> Subject: Re: [PATCH 2 of 2] add support for setting worker processes<br>> and CPU affinity automatically<br>> Message-ID:<br>> <CAOKiq2ADiejbL4SF7DDTqrMHntpf0tD2R1A_-fxJWNQs0O+j_g@mail.gmail.com><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> Hi,<br>> <br>> On Fri, Jan 13, 2012 at 6:33 PM, Valentin V. Bartenev <ne@vbart.ru> wrote:<br>> <br>> > On Friday 13 January 2012 14:04:11 Joshua Zhu wrote:<br>> ><br>> <br>> [snip]<br>> <br>> <br>> > So, when you need some automation for configuration and deployment, the<br>> > better<br>> > solution would be using proper software for that task, isn't it? Like<br>> > Puppet,<br>> > for example.<br>> ><br>> ><br>> OK.<br>> If this patch would not be accepted, could you please also review the first<br>> one?<br>> Thank you.<br>> <br>> Regards,<br>> <br>> -- <br>> Joshua Zhu<br>> Senior Software Engineer<br>> Server Platforms Team at Taobao<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20120113/f130682d/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 4<br>> Date: Fri, 13 Jan 2012 17:18:51 +0400<br>> From: Maxim Konovalov <maxim@nginx.com><br>> To: nginx@nginx.org<br>> Subject: Re: [PATCH 2 of 2] add support for setting worker processes<br>> and CPU affinity automatically<br>> Message-ID: <4F102F3B.5050506@nginx.com><br>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>> <br>> On 1/13/12 2:27 PM, Piotr Sikora wrote:<br>> > Hi,<br>> ><br>> >>> Setting CPU affinity is available on Linux systems only. Please<br>> >>> correct me if I'm wrong.<br>> >><br>> >> That's wrong.<br>> ><br>> > I believe that Joshua meant that workers CPU affinity _in nginx_<br>> > works only on Linux right now (which is true).<br>> ><br>> Ah, I see, thanks.<br>> <br>> I just wonder how useful this option in real environment.<br>> <br>> -- <br>> Maxim Konovalov<br>> +7 (910) 4293178<br>> http://nginx.com/<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Fri, 13 Jan 2012 08:36:20 -0500<br>> From: "double" <nginx-forum@nginx.us><br>> To: nginx@nginx.org<br>> Subject: Limit robots<br>> Message-ID:<br>> <6300b8a589bb337813f7df86d393d332.NginxMailingListEnglish@forum.nginx.org><br>> <br>> Content-Type: text/plain; charset=UTF-8<br>> <br>> Hello,<br>> <br>> Is there a chance to limit robots to 1 request per second?<br>> The down below does not work: [emerg] "limit_req" directive is not<br>> allowed here<br>> <br>> Thanks a lot<br>> Markus<br>> <br>> <br>> http {<br>> limit_req_zone $http_user_agent zone=useragenttrack:1m <br>> rate=1r/s;<br>> server {<br>> listen 80;<br>> location / {<br>> if ($http_user_agent ~* "[a-z]bot[^a-z]") {<br>> limit_req zone=useragenttrack burst=100 nodelay;<br>> }<br>> }<br>> }<br>> }<br>> <br>> Posted at Nginx Forum: http://forum.nginx.org/read.php?2,221162,221162#msg-221162<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 6<br>> Date: Fri, 13 Jan 2012 08:44:13 -0500<br>> From: "andres-m77" <nginx-forum@nginx.us><br>> To: nginx@nginx.org<br>> Subject: help with replacing chars "_" to "." in a $variable<br>> Message-ID:<br>> <7770f2f8745407086920bd36c17248d1.NginxMailingListEnglish@forum.nginx.org><br>> <br>> Content-Type: text/plain; charset=UTF-8<br>> <br>> I would appreciate your help<br>> <br>> I have to do the following request<br>> <br>> http://subdomain_domain_extension_tdl.domain.com/<br>> <br>> Where .domain.com must be deleted and subdomain_domain_extension_tdl<br>> must be converted to subdomain.domain.extension.tdl<br>> <br>> <br>> I did this:<br>> <br>> set $subdomain "";<br>> <br>> if ($host ~* "^(.+)\.domain\.com$") {<br>> set $subdomain $1;<br>> break;<br>> }<br>> <br>> resolver 8.8.8.8;<br>> proxy_pass http://$subdomain;<br>> proxy_set_header X-Real-IP $remote_addr;<br>> <br>> <br>> Then i get $subdomain as: subdomain_domain_extension_tdl but i need to<br>> transform it into subdomain.domain.extension.tdl<br>> <br>> Could you please help me determining how could i do this? i would like<br>> to serve as proxy in this way:<br>> <br>> <br>> If you want to get inside any blocked website like www.facebook.com be<br>> able to do it throug www_facebook_com.domain.com<br>> <br>> Also i know that perhaps sometimes subdomain_domain_extension_tdl could<br>> be domain_extension_tdl, <br>> <br>> <br>> Thanks in advance!<br>> Andr?s<br>> <br>> Posted at Nginx Forum: http://forum.nginx.org/read.php?2,221176,221176#msg-221176<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 7<br>> Date: Fri, 13 Jan 2012 13:50:48 +0000<br>> From: Ant?nio P. P. Almeida <appa@perusio.net><br>> To: nginx@nginx.org<br>> Subject: Re: Limit robots<br>> Message-ID: <874nvzyamf.wl%appa@perusio.net><br>> Content-Type: text/plain; charset=US-ASCII<br>> <br>> On 13 Jan 2012 13h36 WET, nginx-forum@nginx.us wrote:<br>> <br>> > Hello,<br>> ><br>> > Is there a chance to limit robots to 1 request per second?<br>> > The down below does not work: [emerg] "limit_req" directive is not<br>> > allowed here<br>> <br>> Yes. Try:<br>> <br>> At the *http* level:<br>> <br>> limit_req_zone $http_user_agent zone=useragenttrack:1m rate=1r/s; <br>> <br>> map $http_user_agent $is_bot {<br>> default 0;<br>> ~[a-z]bot[^a-z] 1;<br>> }<br>> <br>> At the server level:<br>> <br>> location / {<br>> error_page 418 @bots;<br>> <br>> if ($is_bot) {<br>> return 418; <br>> }<br>> ...<br>> }<br>> <br>> location @bots {<br>> limit_req zone=useragenttrack burst=100 nodelay; <br>> ...<br>> }<br>> <br>> Cf: http://wiki.nginx.org/HttpLimitReqModule<br>> <br>> --- appa<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 8<br>> Date: Fri, 13 Jan 2012 11:57:30 -0200<br>> From: Martin Loy <martinloy.uy@gmail.com><br>> To: nginx@nginx.org<br>> Subject: Re: Programmatic access to Nginx fcgi/proxy cache?<br>> Message-ID:<br>> <CAHbGeW6f0xq6AyeZxGjcRb=p-5aMWdFP5Y7sBVUTSdQ3M5EZ3A@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Ben<br>> <br>> Why not use memcached/redis/etc as cache backend instead of file based<br>> cache, nginx works with them great and you just need to populate the cache<br>> at application level :)<br>> <br>> http://wiki.nginx.org/HttpMemcachedModule<br>> http://wiki.nginx.org/HttpRedis<br>> <br>> Regards<br>> <br>> M<br>> <br>> <br>> On Thu, Jan 12, 2012 at 4:56 PM, Piotr Sikora <piotr.sikora@frickle.com>wrote:<br>> <br>> > Hi,<br>> ><br>> ><br>> > There's also a 3rd party module for cache purging. AFAIK doesn't<br>> >> support wildcards:<br>> >><br>> >> https://github.com/FRiCKLE/**ngx_cache_purge<https://github.com/FRiCKLE/ngx_cache_purge><br>> >><br>> ><br>> > It doesn't, but because of that it's the only one of those mentioned that<br>> > works at scale.<br>> ><br>> > Best regards,<br>> > Piotr Sikora < piotr.sikora@frickle.com ><br>> ><br>> ><br>> > ______________________________**_________________<br>> > nginx mailing list<br>> > nginx@nginx.org<br>> > http://mailman.nginx.org/**mailman/listinfo/nginx<http://mailman.nginx.org/mailman/listinfo/nginx><br>> ><br>> <br>> <br>> <br>> -- <br>> *Nunca hubo un amigo que hiciese un favor a un enano, ni un enemigo que le<br>> hiciese un mal, que no se viese recompensado por entero.*<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20120113/8eaa408c/attachment.html><br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> nginx mailing list<br>> nginx@nginx.org<br>> http://mailman.nginx.org/mailman/listinfo/nginx<br>> <br>> End of nginx Digest, Vol 27, Issue 33<br>> *************************************<br></div></div> </div></body>
</html>