Show all posts by user
What you would like to see here at the site
Re: Specific permissions for fastcgi_temp_path? - 10 years ago
I have the same scope for directories, I need to have them defined at 0750, instead of 0700: # ls -lha /var/lib/nginx/fastcgi total 4.0K drwxr-x---. 6 nginx root 120 Aug 10 14:09 . drwxr-xr-x. 9 root root 4.0K Aug 5 20:38 .. drwx------. 3 nginx nginx 60 Aug 10 14:09 1 drwx------. 3 nginx nginx 60 Aug 10 14:09 3 drwx------. 3 nginx nginx 60 Aug 10 14:09 4 drwx------. 2 nginx rootby TECK - Nginx Mailing List - English
Specific permissions for fastcgi_temp_path? - 10 years ago
Hi all, I looked into /src/core/ngx_file.c and noticed that ngx_conf_set_access_slot() defines the access type. What is the variable I need to use in order to force new files to be written 0640, instead of 0600 as access defines it? I tried, without success: fastcgi_temp_path /var/lib/nginx/fastcgi 1 2; fastcgi_store_access user:rw group:r; Thank you for your hby TECK - Nginx Mailing List - English
Re: Nginx 1.7.0: location @php - 10 years ago
Jonathan Matthews Wrote: ------------------------------------------------------- > Fortunately, this being a *public* *mailing* *list*, and Francis > (along with almost every other subscriber) giving his time, experience > and opinions for free, you are definitely no worse off than when you > started. > > Actually, however, you're demonstrably better off, as Francis has bby TECK - Nginx Mailing List - English
Re: Nginx 1.7.0: location @php - 10 years ago
support Wrote: ------------------------------------------------------- > yes. > > update and test > > 02.06.2014 10:24, wishmaster пишет: > > I have the same problem in my php-application. Admin folder is > protected with auth_basic and the rest folders - without auth. I have > not found any solution except code duplication for php location. Can youby TECK - Nginx Mailing List - English
Re: Nginx 1.7.0: location @php - 10 years ago
Francis, We are going in circles without reaching a solution. I think what I asked is very clear and simple: How do I avoid repeating a segment of configuration code assigned to @php into various locations: location @php { try_files $uri =404; fastcgi_split_path_info ^(.+\.php)(/.+)$; fastcgi_pass fastcgi; fastcgi_param PATH_INFO $fastcgi_path_info; fastcgi_param PATH_TRANSLATED $doby TECK - Nginx Mailing List - English
Re: Nginx 1.7.0: location @php - 10 years ago
Francis, > I'm guessing that you may want something like > try_files i-dislike-macro-include @php; What you posted is some deprecated configuration available on Google. > Perhaps the request that you made did not match the location blocks that you showed? If that would be the case, the proper code posted earlier would not work, so this is not the case. I'm very familiar with Nginby TECK - Nginx Mailing List - English
Re: Nginx 1.7.0: location @php - 10 years ago
Hi Francis, > Answer #1: what does "does not work" mean? When I process an URI request, it downloads the file instead of executing the PHP code. What I try to achieve is very simple, use @php as location to execute PHP code instead of repeating it over and over in various locations. Here it is a better example of a functional setup: http://pastie.org/private/5gkl1pti1co0onzhgbby TECK - Nginx Mailing List - English
Nginx 1.7.0: location @php - 10 years ago
Hi all, I'm trying to understand why the use of this configuration code does not work: location ^~ /setup { auth_basic "Restricted Access"; auth_basic_user_file htpasswd; try_files $uri $uri/ /setup/index.php?$uri&$args; location ~ \.php$ { try_files @php =404; } } location @php { try_filesby TECK - Nginx Mailing List - English
Redirect loop fixed, I need a better rule format - 10 years ago
Hello everyone, I have a little problem on hand, related to redirect loop for a specific location: server { listen 192.168.1.2:443 spdy ssl default_server; ... location ^~ /alpha { return 301 https://www.domain.com$request_uri; } ... } I would like to redirect URL's of this format: https://www.domain.com/alpha/delta/ To: https://www.domain.com/delta/ I can access fine the httby TECK - Nginx Mailing List - English
Re: Redirection issues - 11 years ago
Thank you Maxim. :) Is there a way to skip the IF with try_files and still having a 301 footprint? Something like: try_files /beta/info/$arg_id/ =404;by TECK - Nginx Mailing List - English
Redirection issues - 11 years ago
Hello everyone, I'm currently using Nginx 1.4.1 on CentOS 6.4 64bits and trying to perform a redirect of this type: location /alpha { location ~ ^/alpha/script.+([\d]+)$ { return 301 /beta/info/$1/; } } The originating location is /alpha/script.php?id=328. The redirected location is /beta/info/328/. For some reason, the above redirect returns a 404 with the URL: httby TECK - Nginx Mailing List - English
Full WebDAV support? - 11 years ago
Hi everyone, I was wondering if there are any plans to add full WebDAV support to native nginx module? Right now I use ngx_http_dav_ext_module.c as complement and I'm wondering what are the reasons why the devs do not add the missing commands. Regards, Florenby TECK - Nginx Mailing List - English
Re: Configure specific upstream node to spit 30x error - 12 years ago
Thank you, Maxim. Related to second part of my question: Will the POST be passed properly to next node, if first one fails? If is not, is there a configuration setting that will enable that feature? Regards, Florenby TECK - Nginx Mailing List - English
Re: Configure specific upstream node to spit 30x error - 12 years ago
Just to clarify, my goal is to make sure a php-fpm POST is passed to next node, if current fails. From my understanding the 307 error is designed to do this. Thank you.by TECK - Nginx Mailing List - English
Configure specific upstream node to spit 30x error - 12 years ago
Hi all, I was wondering if there is feasible way to have a node spit a specific 30x error (i.e. 307) if it becomes unreachable, instead of passing to next upstream node? upstream mycluster { server 192.168.1.2; server 192.168.1.3; server 192.168.1.4; } If node 192.168.1.3 is down, it should return a 307, instead of passing to 192.168.1.4. Thank you for your help. Regards, Floby TECK - Nginx Mailing List - English
Re: Force "internal" directive to display a custom 404? - 12 years ago
Hi Maxim, The problem was located somewhere between my seat and the computer screen. :) I forgot to add the error_page 404 /404.html; condition into ssl server... doh. Regards, Florenby TECK - Nginx Mailing List - English
Force "internal" directive to display a custom 404? - 12 years ago
Example: error_page 404 /404.html; location = /404.html { internal; } location /alpha { internal; } The proper behavior would be to display the custom 404.html in every case, which does not. I'm not sure this could be marked as new feature, or is feasible with some configuration I don't know about it? Thanks.by TECK - Nginx Mailing List - English
PROPFIND and OPTIONS support in Nginx? - 12 years ago
I was wondering why the Nginx devs do not add WebDAV support for PROPFIND and OPTIONS. There is a module available in Github but still, I would love to have this officially supported by Nginx: https://github.com/arut/nginx-dav-ext-module Are there any plans to have full WebDAV support implemented? This would be a nice addition into 1.3.0 branch. Regards, Floren Munteanu ____________________by TECK - Nginx Mailing List - English
Re: Does nginx plan to support spdy? - 12 years ago
http://trac.nginx.org/nginx/ticket/30 On 4/27/2012 8:12 PM, ctrlbrk wrote: > Firefox 13 (in beta today, scheduled for public release near end of May) > will enable SPDY by default. > > Any update regarding nginx support? > > Posted at Nginx Forum: http://forum.nginx.org/read.php?2,217299,225885#msg-225885 _______________________________________________ nginx mailing list nginx@by TECK - Nginx Mailing List - English
Re: Does auth_basic changes require a service reload? - 12 years ago
Sorry to repeat myself Maxim. The file is looked at startup so if I add a new user or edit an existing password, it will not require a service restart?by TECK - Nginx Mailing List - English
Does auth_basic changes require a service reload? - 12 years ago
Hi, I'm wondering if I need to perform a "service nginx restart", if I do any changes to htpasswd file: location / { auth_basic "closed site"; auth_basic_user_file htpasswd; } I noticed that sometimes it works without reloading the service.by TECK - Nginx Mailing List - English
Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14 - 12 years ago
Hi Maxim, On 4/3/2012 12:32 PM, Maxim Dounin wrote: > I'm afraid we aren't going to fix 1.0.x anyway. The 1.1.x branch > will become stable in serveral weeks, and 1.0.x is expected to get > only security fixes. Thanks, I will install a debug version of 1.1.18 into live server. > For now, please capture debug log. Anything else (including gdb > dump of the request in question) iby TECK - Nginx Mailing List - English
Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14 - 12 years ago
Hi Maxim, On 4/2/2012 1:06 PM, Maxim Dounin wrote: > It's safe and only adds minimal overhead on logging level checks > as long as debug log isn't enabled. > > Note though that writing debug logs consume extra resources, and > it may be noticeable under high load. The debug_connection > directive allows to enable debug logging only for selected ip > addresses to minimize impby TECK - Nginx Mailing List - English
Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14 - 12 years ago
Hi Maxim, On 4/2/2012 7:17 AM, Maxim Dounin wrote: > As already suggested, it whould be cool to check if you see the > same problem in 1.1.x. > > And to proceed further we need debug log, see here: > > http://wiki.nginx.org/Debugging > > Note you'll need to recompile nginx with "--with-debug" configure > argument to obtain one. How safe is to put in productioby TECK - Nginx Mailing List - English
Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14 - 12 years ago
More updates on the SSL issue. I have the following configuration: http { ... ssl_prefer_server_ciphers on; ssl_ciphers RC4:HIGH:!aNULL:!MD5; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_session_cache shared:SSL:5m; ssl_session_timeout 10m; ... } If I disable the ssl_preferby TECK - Nginx Mailing List - English
Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14 - 12 years ago
I mention this because the issues were present in the past with Nginx 0.8 and they were solved by Igor. I was hoping a similar fix would be provided for latest stable version. Do you recommend me to switch to development version? Upgrading openssl is not a viable solution at the present time and we are getting a fairly large number of SSL_write() errors in our logs.by TECK - Nginx Mailing List - English
Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14 - 12 years ago
> That's really strange, changes between 1.0.12 and 1.0.14 are > minimal. Could you please re-try with 1.0.12 to see if it works > for you without problems? Will do, Maxim. I have to rebuild the RPM again, as I tossed the previous version from yum repository. > As already suggested - you may build nginx with any particular > openssl version statically, by using --with-opensslby TECK - Nginx Mailing List - English
Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14 - 12 years ago
I looked into upgrading to 1.0.1, it is not possible. We are talking about 84 package deps, on a minimal install. So upgrading openssl is not viable.by TECK - Nginx Mailing List - English
Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14 - 12 years ago
Hi Maxim, > Do you see this as a regression from some previous version? If > yes - which one? Do you see the same problem in 1.1.x? I used before 1.0.12 and did not experienced the socket leaks. > This usually happens if you update files non-atomically, i.e. edit > files in-place instead of creating new file and then renaming it > to desired name. Obvious solution is toby TECK - Nginx Mailing List - English
Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14 - 12 years ago
This occurs randomly, it is not something constant.by TECK - Nginx Mailing List - English
 |
 |
 |
 |
|