Changes with nginx 0.8.14 07 Sep 2009 *) Bugfix: an expired cached response might stick in the "UPDATING" state. *) Bugfix: a segmentation fault might occur in worker process, if error_log was set to info or debug level. Thanks to Sergey Bochenkov. *) Bugfix: in embedded perl module; the bug had appeared in 0.8.by Igor Sysoev - Nginx Mailing List - English
On Mon, Sep 07, 2009 at 03:05:34AM -0400, pepejose wrote: > UP! UP! > > and the problem with large images with "proxy_buffering on"? (http://www.eglx.com/J/bug.JPG) > > > I have to increase the size of the buffers or configure something else? Have you looked in error_log ? -- Igor Sysoev http://sysoev.ru/en/by Igor Sysoev - Nginx Mailing List - English
On Sun, Sep 06, 2009 at 03:29:48AM -0400, ronin wrote: > I use nginx 07.61 upload files Often fail???using normal apache > nginx.conf: > server_names_hash_bucket_size 128; > client_header_buffer_size 32k; > large_client_header_buffers 4 32k; > client_max_body_size 8m; > sendfile on; > tcp_nopush on; > server_name_in_redirect off; > server_tokensby Igor Sysoev - Nginx Mailing List - English
On Sun, Sep 06, 2009 at 10:32:06AM -0400, ronin wrote: > error info: > Warning: REQUEST_BODY_FILE: open('/dev/shm/client_body_temp/0000000002') failed: No such file or directory (2) in Unknown on line 0 Who show this error ? BTW, does Linux allow to create subdirectories in /dev/shm ? -- Igor Sysoev http://sysoev.ru/en/by Igor Sysoev - Nginx Mailing List - English
On Sun, Sep 06, 2009 at 04:24:31AM -0400, zobo wrote: > Hi. > Many thanks for your reply. > > I do not want it to be ipv6only - I did however find the option in ru docs and source. I want it to be 6 and 4. As it is in case I put listen [::]:80. What I am suggesting is that if nginx is compiled --with-ipv6 that listen is by default [::]:80 instead of 80. > > To be even more desby Igor Sysoev - Nginx Mailing List - English
On Sun, Sep 06, 2009 at 12:17:18PM +0100, Nuno Magalh??es wrote: > Sorry for the slight highjack. I have a similar issue[1][2], and tried: > fastcgi_buffer_size 16k; > fastcgi_buffers 16 16k; > on my nginx.conf. I also tried: > fastcgi_buffer_size 4k; > fastcgi_buffers 64 16k; > and: > fastcgi_buffer_size 16k; >by Igor Sysoev - Nginx Mailing List - English
On Sun, Sep 06, 2009 at 08:29:09AM +0400, Igor Sysoev wrote: > On Sat, Sep 05, 2009 at 11:28:14AM -0500, AMP Admin wrote: > > > Thanks. I'll do that. I was just hoping that I wouldn't have to list all > > domains. That works though. :) > > You should use positive logic: configure all sites and redirect > remainder using regex: > > server { > server_naby Igor Sysoev - Nginx Mailing List - English
On Sun, Sep 06, 2009 at 11:53:48AM +0400, Igor Sysoev wrote: > On Sun, Sep 06, 2009 at 03:39:12AM -0400, zobo wrote: > > > Hi. > > Прежде всего, болшое спасибо дла Nginx. > > > > We are currently very much moving forward with IPv6 and I had a small problem with Nginx and I would like to give a suggestion. The problem was, that if we did nby Igor Sysoev - Nginx Mailing List - English
On Sun, Sep 06, 2009 at 03:39:12AM -0400, zobo wrote: > Hi. > Прежде всего, болшое спасибо дла Nginx. > > We are currently very much moving forward with IPv6 and I had a small problem with Nginx and I would like to give a suggestion. The problem was, that if we did not specify listen [::]:80 to every server declaration, nginx would fail to start. Naturally,by Igor Sysoev - Nginx Mailing List - English
On Sat, Sep 05, 2009 at 11:28:14AM -0500, AMP Admin wrote: > Thanks. I'll do that. I was just hoping that I wouldn't have to list all > domains. That works though. :) You should use positive logic: configure all sites and redirect remainder using regex: server { server_name www.domain1.com; ... } server { server_name www.domain2.com; ... } server { server_nameby Igor Sysoev - Nginx Mailing List - English
On Sat, Sep 05, 2009 at 08:57:57AM -0500, AMP Admin wrote: > Hi, I would like to rewrite several domains to from .example.com to > www.example.com. I think the best way is to use a wild card. Too bad I > suck at rewrite rules. Haha > > Can someone help me make the following work? > > if ($host != 'www.*.com') { > rewrite ^/(.*)$ http://www.*.cby Igor Sysoev - Nginx Mailing List - English
On Sat, Sep 05, 2009 at 12:00:39PM +0200, ice-egal@web.de wrote: > >Hi, > > > >Settings in your / location will not be inherited by those in other > >locations. The proxy_pass directive can only go in location or > >location-if (i.e. an if (...) {...} inside a location), and can't go at > >the server level, so you'd have to define the proxy_pass setting in eacby Igor Sysoev - Nginx Mailing List - English
On Fri, Sep 04, 2009 at 06:17:31PM +0300, Marcus Clyne wrote: > > >>I tried that, but am getting the following message in the error log: > >> > >>2009/09/04 17:10:10 18834#0: *1 zero length URI to proxy, > >>client: 127.0.0.1, server: localhost, request: "GET /ssi/test.shtml > >>HTTP/1.1", subrequest: "/proxy-google/google.com&quoby Igor Sysoev - Nginx Mailing List - English
On Fri, Sep 04, 2009 at 05:34:21PM +0300, Marcus Clyne wrote: > Igor Sysoev wrote: > >On Fri, Sep 04, 2009 at 03:14:42PM +0300, Marcus Clyne wrote: > > > > > >>Hi, > >> > >>>What if for example you want to ssi from a different domain name so > >>>the html is served from http://www.domain.com/ but the ssi uses > >>>wwby Igor Sysoev - Nginx Mailing List - English
On Fri, Sep 04, 2009 at 03:14:42PM +0300, Marcus Clyne wrote: > Hi, > >What if for example you want to ssi from a different domain name so > >the html is served from http://www.domain.com/ but the ssi uses > >www.other.com (which is also hosted on the same nginx instance). > > > > > You could set the SSI command to > > <!--# include virtual="/dby Igor Sysoev - Nginx Mailing List - English
On Fri, Sep 04, 2009 at 02:31:51PM +0200, Ale Ru wrote: > Igor Sysoev wrote: > > On Fri, Sep 04, 2009 at 01:46:01PM +0200, Ale Ru wrote: > > > >> site.com/any-wildcarded-page-name-at-all > >> listen 80; > >> server_name ~^(www\.)?(.+)$; > >> root /var/www/$2/htdocs; > >> > >> location / { > >> try_files $uriby Igor Sysoev - Nginx Mailing List - English
On Fri, Sep 04, 2009 at 01:46:01PM +0200, Ale Ru wrote: > Hi, > > I use FastCGI and try_files with Nginx. > > FastCGI catches all url patterns and render appropriate page. > > It works well for urls like > site.com/some-page > site.com/index.htm > site.com/any-page.htm > site.com/any-wildcarded-page-name-at-all > > But it never works for site root > sby Igor Sysoev - Nginx Mailing List - English
On Fri, Sep 04, 2009 at 02:19:19PM +0300, zepolen wrote: > 2009/9/4 Igor Sysoev <is@rambler-co.ru>: > > On Fri, Sep 04, 2009 at 01:55:50AM +0300, zepolen wrote: > >> Going to directly to http://www.domain.com/ssi/base.html in a browser > >> shows the file ok > >> > >> However if it gets loaded as ssi, the request seems to go to the > >>by Igor Sysoev - Nginx Mailing List - English
On Thu, Sep 03, 2009 at 06:53:41PM -0400, ned0r wrote: > If you use the proxy_cache_key directive as you demonstrated above (i.e. proxy_cache_key "http://cacheserver$request_uri$cookie_user";) then my understanding is: > > If a user doesn't have that cookie set, the page will be cached, and all users who don't have the cookie set will see the same page. > > If a user doby Igor Sysoev - Nginx Mailing List - English
On Fri, Sep 04, 2009 at 01:55:50AM +0300, zepolen wrote: > In the html for the backend app server is: <!--# include > virtual="http://www.domain.com/ssi/base.html" --> > > Going to directly to http://www.domain.com/ssi/base.html in a browser > shows the file ok > > However if it gets loaded as ssi, the request seems to go to the > backend (which says 404)by Igor Sysoev - Nginx Mailing List - English
On Thu, Sep 03, 2009 at 09:11:12AM -0500, David Murphy wrote: > This configure worked on Ubuntu 8.04 with 7.13 but on 7.61 I am getting an > error. I have treid with and without the slash and even ln -s /usr > /usr/openssl to appease the compiler but nothing seems to work. > > Can someone let me know what im doing wrong? > > > > > > # aptitude show lby Igor Sysoev - Nginx Mailing List - English
On Thu, Sep 03, 2009 at 09:06:26AM -0500, AMP Admin wrote: > Haha I don't know Russian. I know you work hard so I'm not complaining. In RSS you may see English word "nginx" and Arabic digits :) > I do think that since nginx is growing so fast this is something that'll > need to be addressed soon. > > Also, if the Announcements forum was used we would be able to justby Igor Sysoev - Nginx Mailing List - English
On Thu, Sep 03, 2009 at 08:28:09AM -0500, AMP Admin wrote: > I looked at the forum and it seems that the Announcements Forum isn't > updated at all. I really want to unsubscribe from this list but I would > like to find feeds on major stable releases and any security news. Is there > an rss feed or list just for those two subjects? > > If not that's a pretty major deal that nby Igor Sysoev - Nginx Mailing List - English
On Thu, Sep 03, 2009 at 03:14:44PM +0200, Tomasz Pajor wrote: > > >On Thu, Sep 03, 2009 at 01:59:52PM +0200, Tomasz Pajor wrote: > > > > > >>For those who would want to use such a setup: > >> > >> location ~ ^/imgheaders/(.*)$ { > >> root /vhosts/static/img/headers; > >> try_files /$1 @headers;by Igor Sysoev - Nginx Mailing List - English
On Wed, Sep 02, 2009 at 06:21:16PM +0200, Robert Gabriel wrote: > Im trying to download the latest version of nginx (0.8.13) but seems the > server is down, especially sysoev.ru. > > Does anyone has the same issue? This was outage. -- Igor Sysoev http://sysoev.ru/en/by Igor Sysoev - Nginx Mailing List - English
On Wed, Sep 02, 2009 at 06:06:34PM -0400, Jim Ohlstein wrote: > Nuno Magalh??es wrote: > >>This does not generate any errors. > >> > >Glad to hear it. > > > > > > > >>(Yes, I also don't like the www prefix.) > >> > >Do you have a specific reason for using two server{ } for the same > >domain? Other than > >by Igor Sysoev - Nginx Mailing List - English
On Wed, Sep 02, 2009 at 08:47:39AM +0100, Nuno Magalh??es wrote: > > This does not generate any errors. > Glad to hear it. > > > > (Yes, I also don't like the www prefix.) > Do you have a specific reason for using two server{ } for the same > domain? Other than > > > This also is *exactly* how Igor suggested that I do it. > > > > But even if Iby Igor Sysoev - Nginx Mailing List - English
On Thu, Sep 03, 2009 at 01:59:52PM +0200, Tomasz Pajor wrote: > For those who would want to use such a setup: > > location ~ ^/imgheaders/(.*)$ { > root /vhosts/static/img/headers; > try_files /$1 @headers; > } location /imgheaders/ { alias /vhosts/static/img/headers/; try_files $uri @headers;by Igor Sysoev - Nginx Mailing List - English
On Thu, Sep 03, 2009 at 12:33:43PM +0200, Tomasz Pajor wrote: > This worked great, but i had to change the request format to: > > http://test.dev/imgheaders/<img_hash>.png?<img_serialize> > > and the image if exists is in /vhosts/static/img/headers/<img_hash>.png > > Can You please update the location statement, because I can't get it right, > thanks!by Igor Sysoev - Nginx Mailing List - English
On Thu, Sep 03, 2009 at 01:20:19PM +0400, Igor Sysoev wrote: > On Thu, Sep 03, 2009 at 11:14:17AM +0200, Tomasz Pajor wrote: > > > I have a request: > > > > http://test.dev/imgheaders/<img_hash>/<img_serialize> > > > > What I want to achieve is, get from location <img_hash>, and check if > > file exists, if it exists then serve theby Igor Sysoev - Nginx Mailing List - English
![]() |
![]() |
![]() |
![]() |
|