I'm sorry, I did not understood nothing. Can you provide an example of how
to avoid repeating the php configuration through @php location?
As someone said in earlier mails you can always use include and put the
repeating parts in seperate files.
For example put this into php.conf:
location ~
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
> start
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 so
On 2 June 2014 04:47, TECK wrote:
> Francis,
>
> We are going in circles without reaching a solution
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
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.
--- Original message ---
Fr
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.
--- Original message ---
From: "TECK"
Date: 2 June 2014, 06:47:47
> Francis,
>
> We
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)(/.+
On Sat, May 31, 2014 at 06:31:09AM -0400, TECK wrote:
Hi there,
>> 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.
That's a reasonable assumption to mak
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 cod
On Sat, May 31, 2014 at 01:59:18AM -0400, TECK wrote:
Hi there,
> > Answer #1: what does "does not work" mean?
> When I process an URI request, it downloads the file instead of executing
> the PHP code.
Perhaps the request that you made did not match the location blocks that
you showed?
That's
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
On Sun, May 25, 2014 at 05:49:33AM -0400, TECK wrote:
Hi there,
> I'm trying to understand why the use of this configuration code does not
> work:
Answer #1: what does "does not work" mean?
What request do you make; what response do you get; what response do
you want?
> try_files
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_filehtpasswd;
try_files $uri $uri/ /setup/index.php?$uri&$args;
thanks for the reply and fix :)
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,249586,249595#msg-249595
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
I'm one of the Phusion Passenger authors. For Phusion Passenger support,
please use the Phusion Passenger discussion forum, not the Nginx forum. It's
here: https://groups.google.com/forum/#!forum/phusion-passenger
This is a compilation problem due to some old code which tries to support
Nginx 0.7.
removing these lines in
/usr/local/rvm/gems/ruby-2.1.1/gems/passenger-4.0.41/ext/nginx/StaticContentHandler.c
seem to have allowed it to compile properly
if (r->zero_in_uri) {
return NGX_DECLINED;
}
nginx -V
nginx version: nginx/1.7.0
built by gcc 4.4.7 20120313 (Red Hat 4.4.
grep -C10 zero_in_uri
/usr/local/rvm/gems/ruby-2.1.1/gems/passenger-4.0.41/ext/nginx/StaticContentHandler.c
if (!(r->method & (NGX_HTTP_GET|NGX_HTTP_HEAD|NGX_HTTP_POST))) {
return NGX_HTTP_NOT_ALLOWED;
}
if (r->uri.data[r->uri.len - 1] == '/') {
return NGX_DECLINED;
--with-pcre-jit --with-http_spdy_module
--add-module=../ngx_pagespeed-release-1.7.30.4-beta
Now when updating to Nginx 1.7.0 fails at this point with both Phusion
Passenger 4.0.37 and 4.0.41
passenger -v
Phusion Passenger version 4.0.41
error message
-o objs/addon/nginx
Hello Nginx users,
Now available: Nginx 1.7.0 for Windows http://goo.gl/rYXbPx (32-bit and
64-bit versions)
These versions are to support legacy users who are already using Cygwin
based builds of Nginx. Officially supported native Windows binaries are at
nginx.org.
Announcements are also
Changes with nginx 1.7.0 24 Apr 2014
*) Feature: backend SSL certificate verification.
*) Feature: support for SNI while working with SSL backends.
*) Feature: the $ssl_server_name variable.
*) Feature: the "if" parame
20 matches
Mail list logo
