est_body
I think in this case I definitely want to use a content handler. I will
point out one item I found confusing is the example cited doesn't show how
to hook up the phase handler to nginx - it will never be called. I am
looking at other modules in order to understand how thi
h: 153
< Connection: keep-alive
<
404 Not Found
404 Not Found
nginx/1.25.3
* Connection #0 to host www left intact
Here is how I am building nginx & my module:
auto/configure --with-debug --with-cc-opt="-fsanitize=address
-DNGX_DEBUG_PALLOC=1" --with-ld-opt="
Greetings nginx,
nginx version: nginx/1.18.0 running an AWS EC2 instance with an Amazon Linux 2
AMI.
Using this nginx.conf for reverse proxy and mutual authentication of some
specialized mobile devices.
server {
listen 443 ssl ;
server_name serviceapi.
s/rate-limits/
#
/etc/letsencrypt/renewal $ ls | wc -l
1647
#
We switched to using SAN Certs whenever possible.
Around 8 years ago I managed a 8000 vHosts Webfarm with a apache. No Issues
ether.
Cheers,
Ben
On Mon, Feb 11, 2019 at 4:16 PM rick_pri
wrote:
> Our current setup is pretty
Hi,
nginx/1.10.0 & PHP 7.0.8
I'm struggling to get NGINX to work with the Slim PHP framework for paths.
The base index.php works fine (e.g. http://example.com works), however
if I try a framework path (e.g. http://example.com/hello/test), NGINX
sends me what Firefox seems to call a "DMS file"
On 27/07/2016 17:39, Reinis Rozitis wrote:
You could try to use the alias instead of root then (
http://nginx.org/en/docs/http/ngx_http_core_module.html#alias ).
I will take a look at that link. Thank you.
In my mind though you're making it complicated.
Perhaps I should clarify conte
On 27/07/2016 16:07, Francis Daly wrote:
405 is usually "Method Not Allowed", such as when you try to POST to a file.
But in this case, you do your own "return 405".
POST was just an example, the config doesn't work with GET or anything else.
What happens if the nginx user does
ls -l "
On 27/07/2016 15:50, Reinis Rozitis wrote:
Which translates to the following error.log entry :
stat()
"/usr/share/path/to/my/lumen/public/directory//public/lumen/"
failed (13: Permission denied), client: 192.168.121.10, server:
my.example.com, request: "POST /lumen/ HTTP/1.1", host: "my.exam
Hi,
I'm having a frustrating time trying to get Lumen (a.k.a Laravel)
working on my NGINX install.
At the moment, the best I can get NGINX to give me is 405 errors. Which
translates to the following error.log entry :
stat()
"/usr/share/path/to/my/lumen/public/directory//public/lumen/"
fa
eader Host $host;
}
Best regards,
Vintila Mihai Alexandru
On 7/2/2016 7:21 PM, Ben wrote:
Hi,
I have a PBX that has a webRTC feature (i.e. you login to PBX website
and you have a virtual handset with all the features).
Is it feasible or possible to use NGINX as a reverse proxy to handle
webRTC
Hi,
I have a PBX that has a webRTC feature (i.e. you login to PBX website
and you have a virtual handset with all the features).
Is it feasible or possible to use NGINX as a reverse proxy to handle
webRTC ?
A basic NGINX config just using proxy_pass doesn't seem to work, so I'm
guessing th
On 16/06/2016 14:14, Edho Arief wrote:
Hi
On Thu, Jun 16, 2016, at 22:11, Edho Arief wrote:
for /demo/ it prints "/demo/"
and
for /demo/hello/x it prints "/demo/hello"
Which looks like their "auto base-path" is setting moving goalposts !!
That doesn't make sense if you actually use my co
>>
>> If it helps, I'm using bramus router and my configured paths are as
>> follows :
>>
>
> Looks like the logic for getting base path is a bit interesting. Try
> this for related line:
>
> fastcgi_param SCRIPT_NAME /demo/;
>
That didn't work unfortunatley.
Just dug up their code and I see wh
Hi,
Based on scraps found in the NGINX docs, I have a semi-working config
that looks as follows :
#
location /demo {
allow 10.0.0.0/8;
deny all;
try_files $uri @pdemo;
}
location @pdemo {
fastcgi_param
Hi,
I'm using haproxy infront of some NGINX instances, but only for some
instances which are being loadbalanced by haproxy, there are other
instances which go straight through.
I realise I need to change the logging format in NGINX to enable
X-Forwarded-For in the access logs.
The question
t 12:17 PM, Ben mailto:ben+ng...@list-subs.com>> wrote:
Hi,
Am suffering with a bit of writer's block when it comes to query
rewrites.
I've got a rewrite rule that looks like :
rewrite ^/api/app/([^/]+)/([^/]+)/([^/]+)?$
/api/app/$1.php?p=$2&q=$3? last;
Hi,
Am suffering with a bit of writer's block when it comes to query rewrites.
I've got a rewrite rule that looks like :
rewrite ^/api/app/([^/]+)/([^/]+)/([^/]+)?$ /api/app/$1.php?p=$2&q=$3? last;
I am having two problems :
- I am getting 404 when I try to make a POST call to /api/app/login,
On 2/16/2015 3:52 PM, Francis Daly wrote:
> On Mon, Feb 16, 2015 at 02:55:51PM -0500, Ben Johnson wrote:
>
> Hi there,
>
Hi, Francis, and thank you for taking the time to review my question and
respond. I value and appreciate your time.
>> I've recently compiled nginx-1.
c configuration directive that I've overlooked?
Thanks for any help!
-Ben
###
http {
server {
listen *:443 ssl;
location ^~ /
On 12/13/2014 7:10 PM, Valentin V. Bartenev wrote:
> On Saturday 13 December 2014 18:58:54 Ben Johnson wrote:
> [..]
>> Hello,
>>
>> I apologize for the 4-month delay in responding. :)
>>
>> In particular, I need to have the ability to track upload progress
On 8/22/2014 7:12 PM, Valentin V. Bartenev wrote:
> On Friday 22 August 2014 17:54:22 Ben Johnson wrote:
> [..]
>>
>> Thank you kindly, Valentin. That explains it!
>>
>> Well, that's a real disappointment. Is it no longer possible for nginx
>> to handle
On 8/22/2014 3:05 AM, Valentin V. Bartenev wrote:
> On Thursday 21 August 2014 21:02:43 Ben Johnson wrote:
>> Hello!
>>
>> I performed a dist-upgrade, from Ubuntu 12.04 LTS to 14.04 LTS, and once
>> the dust had settled, nginx refused to start with:
>>
&g
On 8/21/2014 9:02 PM, Ben Johnson wrote:
> # nginx -V
> nginx version: nginx/1.6.0
I should add also that immediately after the upgrade from version 12.04
to 14.04 of my OS, this problem was present, and my nginx version was
1.4.6. The reason for which my current config (quoted above) shows
is supposed to
include all of the most commonly used modules, yet the problem persists.
It seems unlikely that the name of this directive changed. What other
explanations are there?
Thanks for any ideas! Full configuration provided below.
-Ben
# nginx -V
nginx version: nginx/1.6.0
TLS SNI suppo
//en.wikipedia.org/wiki/Server_Name_Indication#Client_side
Makes sense! And I can live with the SSL warning that results when I
employ the method I described a few posts back.
Thanks again for your help, everyone!
-Ben
___
nginx mailing list
nginx@nginx.org
h
On 3/28/2014 11:45 AM, Maxim Dounin wrote:
> Hello!
>
> On Fri, Mar 28, 2014 at 02:53:18PM +, Jonathan Matthews wrote:
>
>> On 28 March 2014 14:31, Ben Johnson wrote:
>>> Is there any way to av,oid this certificate being presented, but still
>>&g
icate being presented, but still
return the 444 response under the conditions I've described?
Thanks for any tips here!
-Ben
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On 11/23/2013 12:36 PM, Ben Johnson wrote:
> location ^~ /stage/ {
>> root /var/www/example.com/private/stage/web/;
>> # The files are read from
>> /var/www/example.com/private/stage/web/stage/
>> index index.php index.html index.htm;
>
On 11/23/2013 3:47 PM, Francis Daly wrote:
> On Sat, Nov 23, 2013 at 01:11:46PM -0500, Ben Johnson wrote:
>> On 11/23/2013 12:36 PM, Ben Johnson wrote:
>
> Hi there,
>
>>> It's bizarre. At some point while meddling with the configuration,
>>> requests
On 11/23/2013 12:36 PM, Ben Johnson wrote:
> Okay, I'm trying to implement this, but something seems to have gone
> terribly awry. I apologize for derailing our progress, but until this is
> resolved, I have no way to test your recommendations.
>
> It's bizarre. At
On 11/21/2013 3:45 PM, Francis Daly wrote:
> On Wed, Nov 20, 2013 at 10:31:07PM -0500, Ben Johnson wrote:
>> On 11/20/2013 4:10 AM, Francis Daly wrote:
>
> Hi there,
>
>>> If you do have free choice in the matter, some things work more easily
>>> within
ation with my particular directory
structure? I'm a bit surprised at how difficult it is to decouple the
request location from the filesystem directory from which it is served,
while maintaining this clean-URL setup.
>>> You may want to use something other than $uri in the last argument to
>>> try_files, depending on how you want /stage/my-account/?key=value to
>>> be processed.
>
> The usual caveats apply here regarding url escaping -- you've copied
> an unescaped string directly into query string, so if there were any
> characters like % or + or & involved, they may cause confusion.
>
Understood. The snippet that I pasted above does everything that I
want/need with respect to escaping (or not), so if that can be made to
work with minimal "tweaking", it would be ideal.
> Cheers,
>
> f
>
Thanks again for your time, dedication, and assistance. I'm very grateful!
-Ben
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On 11/19/2013 3:39 PM, Francis Daly wrote:
> On Tue, Nov 19, 2013 at 01:45:15PM -0500, Ben Johnson wrote:
>> On 11/19/2013 12:38 PM, Francis Daly wrote:
>>> On Tue, Nov 19, 2013 at 10:36:53AM -0500, Ben Johnson wrote:
>
> Hi there,
>
>>>> This work
On 11/19/2013 12:38 PM, Francis Daly wrote:
> On Tue, Nov 19, 2013 at 10:36:53AM -0500, Ben Johnson wrote:
>
> Hi there,
>
>> This works as expected, with one major exception: "clean-URL" rewriting
>> does not work. In other words, the homepage (/stage/) loa
ot;primary script unknown" when using
# the "break" keyword, and redirect cycle when using
# the "last" keyword.
rewrite '^(.*)$' /stage/index.php?q=$1 break;
}
}
Any assistance with making this to work
ase, it would be good idea to use least_conn balancer
> here.
>
> http://nginx.org/r/least_conn
>
Cool, this looks great.
Thanks for providing a full, concrete example, itpp2012! That's hugely
helpful!
I'll bear in mind your advice regarding least_conn balancer, too, Maxim.
Thanks again, guys!
-Ben
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On 10/10/2013 11:26 AM, Maxim Dounin wrote:
> Hello!
>
> On Thu, Oct 10, 2013 at 11:13:40AM -0400, Ben Johnson wrote:
>
> [...]
>
>> Well, after all of the configuration changes, both to nginx and PHP, the
>> solution was to add the following header to the r
ee the Windows limitation, "Although several workers can be
started, only one of them actually does any work", but that isn't the
problem here, right? One nginx worker does not mean that only one PHP
request can be satisfied at a time, correct?
Thanks again for all the help, everyone!
-Ben
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On 9/16/2013 1:19 PM, Ben Johnson wrote:
> Hello,
>
> In an effort to resolve a different issue, I am trying to confirm that
> my stack is capable of servicing at least two simultaneous requests for
> a given PHP script.
>
> In an effort to confirm this, I have written a s
Hello,
In an effort to resolve a different issue, I am trying to confirm that
my stack is capable of servicing at least two simultaneous requests for
a given PHP script.
In an effort to confirm this, I have written a simple PHP script that
runs for a specified period of time and outputs the numbe
aximum verbosity.
I'll try increasing nginx's logging verbosity, though.
>
>
>
> Regards,
>
> Lukas
Thanks for your helpful insights here, Lukas!
-Ben
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Nothing at all ... I promise you ! (I've been tail -f'ing the logs) ,
and I can promise you its not a DNS problem because I can see the NGINX
default website on port 80 ;-)
I found a workaround setting "proxy_buffering off;" in nginx makes it
work again. Don't know if this is the way it's sup
Hi,
I've tried this with NGINX 1.4.1-1ppa1~precise and node v0.10.17 and
just can't get it to work.
What I've tried / what happens :
(a) Yes, I have tested this direct between client code and node
listening on 0.0.0.0 and it works as expected
(b) I have tried a multitude of alternative config
ther troubleshooting tips would be
much appreciated.
Thanks!
-Ben
On 8/24/2013 5:29 AM, itpp2012 wrote:
> set PHP_FCGI_CHILDREN=0
> set PHP_FCGI_MAX_REQUESTS=1
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,242154,242181#msg-242181
>
> _
On 8/23/2013 3:23 PM, Maxim Dounin wrote:
> Hello!
>
> On Fri, Aug 23, 2013 at 02:41:43PM -0400, Ben Johnson wrote:
>
>>
>>
>> On 8/23/2013 2:05 PM, Maxim Dounin wrote:
>>> Hello!
>>>
>>> On Fri, Aug 23, 2013 at 12:46:44PM -0400,
On 8/23/2013 2:05 PM, Maxim Dounin wrote:
> Hello!
>
> On Fri, Aug 23, 2013 at 12:46:44PM -0400, Ben Johnson wrote:
>
>> Hello,
>>
>> I'm seeing a strange problem with nginx (1.5.2 on Windows) and PHP
>> (5.4.8 on Windows).
>>
>> Whenever
ng the same script under Apache and it functions as
expected with peer verification disabled.
Thank you for any help,
-Ben
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
utput in PHP, all of the output is sent to the
instance of cmd.exe (the Windows console) in which PHP's "php-cgi.exe"
is running. This enables me to see that nginx is indeed handling the
request. Here is the output:
* About to connect() to ben-pc port 443 (#0)
* Trying fe80::
On 7/9/2013 5:47 PM, Francis Daly wrote:
> On Tue, Jul 09, 2013 at 04:48:27PM -0400, Ben Johnson wrote:
>
> Hi there,
>
>> I am working with a server configuration that is partly outside of my
>> control,
>
> I suspect that that's not the intended use c
ble for me to overwrite the values that are defined on the
line "include /etc/nginx/fastcgi_params;" from within the included file
that I can modify, "my-include.conf"?
In particular, I would like to hard-code the SERVER_NAME value within
"my-include
bly to ensure that it will *never* exist).
Perhaps this file is created in "Maintenance Mode", thereby causing all
requests to be redirected to the maintenance message page?
Thanks!
-Ben
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
rox 1-2 mins from first request) response is returned within
> 50-100 msec, as I understand from some cache.
Are you using some type of opcode-caching software, e.g. APC, memcached,
etc.? If you're convinced that PHP is doing the caching, I would disable
any opcode-caching s
On 6/27/2013 7:13 PM, Francis Daly wrote:
> On Thu, Jun 27, 2013 at 01:02:30PM -0400, Ben Johnson wrote:
>> On 6/27/2013 12:42 PM, Ben Johnson wrote:
>
> Hi there,
>
>>> I don't want PMA (anything within the /pma/ location) to be accessible
>>> over
On 6/27/2013 1:15 PM, B.R. wrote:
> Hello,
>
> On Thu, Jun 27, 2013 at 1:02 PM, Ben Johnson <mailto:b...@indietorrent.org>> wrote:
>
>
>
> On 6/27/2013 12:42 PM, Ben Johnson wrote:
> > I don't want PMA (anything within the /pma/ location)
On 6/27/2013 12:42 PM, Ben Johnson wrote:
> I don't want PMA (anything within the /pma/ location) to be accessible
> over a plaintext connection. In other words, I wish to force HTTPS.
>
> Do I need to add something something like this to the location block?
>
&
On 6/27/2013 12:42 PM, Ben Johnson wrote:
> I'm not the type to accept "good enough". I want it to be perfect :).
>
> What would be your preferred course of action to eliminate the internal
> rewrite and instead perform an external redirect for /pma, /PMA, and
>
On 6/26/2013 5:33 PM, Francis Daly wrote:
> On Wed, Jun 26, 2013 at 10:22:21AM -0400, Ben Johnson wrote:
>
> Hi there,
>
>> I was able to accomplish my objective with some help from the tutorial
>> at:
>
> It's good that you've got it working now.
&g
osted previously and the snippet above,
which actually works, I would be most appreciative.
Thank you!
-Ben
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
ndex.php HTTP/1.1" 404 200 "-"
I must be doing something completely asinine.
Other misc. details:
- PHP's open_basedir directive includes the path /var/www/pma.
- nginx is executing the request as the user "web2" who is in t
On 6/18/2013 5:55 PM, Francis Daly wrote:
> On Tue, Jun 18, 2013 at 03:22:04PM -0400, Ben Johnson wrote:
>
> Hi there,
Hi, Francis! I really appreciate your help and your time. Thanks for
replying in such detail.
>> The try_files directive is brilliant. The only problem I'
m" (more an inconvenience, really) is that using
try_files in the manner described in the cited documentation causes the
trailing ampersand ("&") to be appended to "q" even when there are no
$args. Is this behavior intentional? Maybe there's an RFC of which I"m
unaware that lead to this decision.
Thanks for any help!
-Ben
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
sing, but now I know for next time :)
Cheers
Ben
On 24 March 2013 14:56, Ben Hoskings wrote:
> Hi all, I've found a strange behaviour with proxy_pass. I've reduced a
> simple vhost that reproduces it:
>
> server {
> listen 127.0.0.1:8000;
> location /
works correctly:
> curl -I -X GET http://localhost:8000/test-path
> nc -l 127.0.0.1 9000
GET /test-path HTTP/1.0
I ran these tests on nginx-1.2.7 / OS X 10.8.3; the behaviour is the same
on nginx-1.2.4 / Ubuntu 12.04 (which is where I discovered it).
Am I using $scheme i
63 matches
Mail list logo
