This is perfect, just what I needed! Thanks a lot Moshe!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,285079,285082#msg-285082
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
I’m wondering if you are overthinking this. You said that the memory was reused
when the workload increased again. Linux memory management is unintuitive. What
would happen if you used a different metric, say # active connections, as your
autoscaling metric? It sounds like this would behave “bet
If your application is using fastcgi or proxy configuration in nginx, you
need to have nginx put the information from the certificate into a FastCGI
parameter or an http header that your application can read.
Use something like `fastcgi_param DN $ssl_client_s_dn;` for FastCGI or
`proxy_set_header
Hi,
My application uses NGINX as its web server and I am adding support for
client certificate authentication. I have a requirement where after NGINX
validates the client certificate and provides access to my application, I
need to obtain the Subject field of the client certificate to parse certai
yeah that's a good point and let me try out that.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,284983,285078#msg-285078
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Wed, Jul 31, 2019 at 05:29:37PM +0200, Vincent M. wrote:
Hi there,
> I have specified charset and overried_charset on both server and location
> and yet, it was still sending headers in UTF-8.
What does the error log say?
Is there something like
no "charset_map" between the charsets "utf-
On Thu, Jul 25, 2019 at 04:07:57AM -0400, blason wrote:
Hi there,
> My reverse proxy set it up as www.example.com and location / is set it as
> location / {
> proxy_pass https://www.example.com:8084;
> Now URL is getting opened properly when I login it again diverts to port 88
> on the s
On Thu, Jul 25, 2019 at 12:02:27PM +, Andrew Andonopoulos wrote:
Hi there,
> Nginx decide which content to cache based on the configuration under
> "Location" + the cache key? For example I have proxy_cache which means will
> cache everything which match the specific location?
>
nginx cac
On Thu, Aug 01, 2019 at 09:44:20AM -0400, abkulkar wrote:
Hi there,
> I want to build nginx with the debug options and use it in production.
> But the instructions provided here:
> https://nginx.org/en/docs/debugging_log.html do not say if it will have
> performance issues even when I DON'T enabl
On Thu, Aug 01, 2019 at 01:16:45PM +0200, Marcello Lorenzi wrote:
Hi there,
just as a small interruption...
> It seems that the set variable is not
> working into the if statement.
"if" inside "location" is not great to use, unless you know what it does.
> We can’t use the “map” parameter beca
On Wed, Jul 31, 2019 at 11:45:58AM -0500, J. Lewis Muir wrote:
> On 07/31, Francis Daly wrote:
> > On Tue, Jul 30, 2019 at 05:12:01PM -0500, J. Lewis Muir wrote:
Hi there,
> > As in: your request for "/foo" does not match any location{}, and so is
> > handled at server-level, which runs the files
I want to build nginx with the debug options and use it in production.
But the instructions provided here:
https://nginx.org/en/docs/debugging_log.html do not say if it will have
performance issues even when I DON'T enable debug level logging.
The reason to build nginx with debug options is to qui
Hi,
I have a backend server behind nginx (version 1.12.1) which acts as a reserve
proxy. Everything works fine when the responses from the backend is small.
However, if the backend server's response is big (> 85K), then the nginx will
return the first 85941 bytes in the response body, and then t
Hi Max.
In our idea with this configuration all the requests use the sslclient
logformat and in case of failure with the certificate the logformat that
will be used is sslclientfull.
Into the location / we enable the ssl_verify_client to optional and
actually we have some if with the variabile
Hello!
On Thu, Aug 01, 2019 at 09:32:20AM +1000, Rob N ★ wrote:
> On Wed, 31 Jul 2019, at 2:11 AM, Maxim Dounin wrote:
> > > I think I see the problem - when using SMTP with SSL and
> > > resolver, read events might be enabled during address
> > > resolving, leading to duplicate
> > > ngx_mail
15 matches
Mail list logo