nginx1.94 ssl use TLS1.0.
server {
listen 443;
server_name a.com;
ssi on;
ssi_silent_errors on;
ssi_types text/shtml;
ssl on;
ssl_certificate
ssl_certificate_key
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers
Hi,
I saw this example at serverfault.com:
server {
...
resolver 127.0.0.1;
set $backend "http://dynamic.example.com:80";;
proxy_pass $backend;
...
}
I have a few questions:
1) If the resolver DNS becomes unavailable (say connection timeout), what
will nginx do? Will it keep
One other question - is the key zone shared between the worker processes?
Or will each worker allocate its own copy?
On Thu, Mar 10, 2016 at 4:18 PM, CJ Ess wrote:
> I will try that now - but shouldn't it be evicting a key if it can't fit a
> new one?
>
>
> On Thu, Mar 10, 2016 at 2:38 PM, Rich
I will try that now - but shouldn't it be evicting a key if it can't fit a
new one?
On Thu, Mar 10, 2016 at 2:38 PM, Richard Stanway
wrote:
> At a guess I would say your key zone is full. Try increasing the size of
> it.
>
> On Thu, Mar 10, 2016 at 8:07 PM, CJ Ess wrote:
>
>> This is nginx/1.9
At a guess I would say your key zone is full. Try increasing the size of it.
On Thu, Mar 10, 2016 at 8:07 PM, CJ Ess wrote:
> This is nginx/1.9.0 BTW
>
>
> On Thu, Mar 10, 2016 at 2:06 PM, CJ Ess wrote:
>
>> Same condition on two more of the servers in the same pool. Reload
>> doesn't resolve t
This is nginx/1.9.0 BTW
On Thu, Mar 10, 2016 at 2:06 PM, CJ Ess wrote:
> Same condition on two more of the servers in the same pool. Reload doesn't
> resolve the issue, but restart does. No limit being hit on disk space,
> inodes, open files, or memory.
>
>
> On Thu, Mar 10, 2016 at 12:12 PM, C
Same condition on two more of the servers in the same pool. Reload doesn't
resolve the issue, but restart does. No limit being hit on disk space,
inodes, open files, or memory.
On Thu, Mar 10, 2016 at 12:12 PM, CJ Ess wrote:
> I have four servers in a pool running nginx with proxy_cache. One of
I have four servers in a pool running nginx with proxy_cache. One of the
nodes started spewing "could not allocate node in cache keys zone" errors
for every request (which gave 500 status). I did a restart and it started
working again.
What conditions cause that error in general?
If it happens ag
hi list,
i have an nginx infront of apaches, and the apacheshold a list of locations
with basic-auth.
i cannot pass the auth-request from the upstream through nginx to
the user, when i access the urls through nginx i get 403 Forbidden,
while direct access sends the correct 401 Authorization Re
One thing: when we disable threads in config, and leave only "senfile on;"
the problem was gone.
So if problem caused by sendfile and non-atomic file updates, why it does
not apeared when threads off ?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,264764,265214#msg-265214
___
10 matches
Mail list logo
