Am 03-04-2017 18:09, schrieb Dynastic Space:
I used a poor example.
The functionality I was interested in was adding a range of application
servers, all part of the same domain.
I think you have the following options.
.) or list every app server in the upstream block
http://nginx.org/en/doc
On Fri, Apr 7, 2017 at 2:53 PM, Larry Martell wrote:
> I have a django app that I serve with nginx. Some requests that the
> app receives start python threads that are not complete when the
> request returns a response to the client. When I run with the django
> devel server the threads continue t
I have a django app that I serve with nginx. Some requests that the
app receives start python threads that are not complete when the
request returns a response to the client. When I run with the django
devel server the threads continue to run to completion. But when I run
with nginx it seems that t
You could use a map to match proxy_pass URI to user names, and then use a
single password file for the auth_basic module.
This removes the need of having specific location URI for each user,
although you could still keep doing it if they are part of your
requirements.
---
*B. R.*
On Fri, Apr 7, 2
Hi Maxim,
I found one way to make this work using lua to set the cache name. It seems
to be working ok, all my tests passed.
""" Lua Script
local resty_md5 = require "resty.md5"
local str = require "resty.string"
local md5 = resty_md5:new();
local posix = require("posix")
local days_30 = 1000 *
I have been searching if it is possible to do a one-to-one mapping,
something like ::
location /9000
{
auth_basic
auth_value username9000:password9000
proxy_pass http://localhost:9000
}
location /9001
{
auth_basic
auth_value username9002:password9002
proxy_pass http://loca
Hi Ruslan,
Thank you for your answer. This makes complete sense and is the reason why
this was happening.
It didn't occur to me before asking the question - thank you for your help!
On Thu, Apr 6, 2017 at 11:50 PM, Ruslan Ermilov wrote:
> On Thu, Apr 06, 2017 at 11:18:02PM +0200, Michal Kralik
Hi All.
We have setup multiple ssh-reverse tunnels, and our server will be
listening to ports from 9000 to 1.
The server will have a public-IP, and we DO NOT want just anyone to look
into any of the ports by trying ::
http://1.2.3.4:9000
http://1.2.3.4:9001 and so on ...
So, we are wonderin
