> so all goes in the same nginx.conf but in different http{} block or do I need
> one nginx.conf for each, the user unix sockets and also the parent proxy
> server?
A typical nginx configuration has only one http {} block.
You can look at some examples:
https://nginx.org/en/docs/http/request_p
This allows permission management via user accounts but it can can get bulky as soon as you set up user accounts for permission management of each backend application, as they pose a higher risk, as indicated in the previous email
Well you as
> This allows permission management via user accounts but it can can get bulky
> as soon as you set up user accounts for permission management of each backend
> application, as they pose a higher risk, as indicated in the previous email
Well you asked how to proxy unix sockets...
> that is al
Hello Nginx users,
Now available: Nginx 1.15.5 for Windows
https://kevinworthington.com/nginxwin1155 (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.
Announce
Changes with nginx 1.15.502 Oct 2018
*) Bugfix: a segmentation fault might occur in a worker process when
using OpenSSL 1.1.0h or newer; the bug had appeared in 1.15.4.
*) Bugfix: of minor potential bugs.
--
Maxim Dounin
http://nginx.org/
On Mon, Oct 01, 2018 at 12:22:59PM -0700, Brian W. wrote:
> I have gotten the ldap setup working with their backend-sample-app.py file
> properly and it displays the hello world message. What I cannot figure out
> is how to redirect it to another url on another machine, as opposed to that
> local p
Hello!
On Tue, Oct 02, 2018 at 08:34:25AM +0530, Quintin Par wrote:
> Relevant code:
>
> proxy_cache_valid 200 301 302 1d;
>
> proxy_cache_use_stale error timeout invalid_header updating http_500
> http_502 http_503 http_504;
>
> proxy_cache_background_update on;
>
> proxy_cache_lock on;
>
thx that gets me closer to the end :).
let's try to summarize it (and add some more info):
proxy and unix socket,
This allows permission management via user accounts but it
can can get bulky as soon as you set up
Hi all,
Based on googling, i found some of the Mail proxy config as per below.
Question is, is that config is valid for both as Web server and Mail proxy?
[root@ns2 conf]# more nginx.conf
worker_processes 1;
events {
worker_connections 1024;
}
http {
include mime.types;
