Hi Liu Peng.
We still don't know your nginx version nor your config!
Cite from below:
So now the standard Questions from me:
What's the output of nginx -V ?
What's your config?
regards
aleks
Am 07-03-2017 02:37, schrieb t...@sina.com:
Hi, Alexks,
I try your proposal and it doesn't work. Ac
Thank you Maxim, my reading is wrong, this line of code is in function
ngx_ssl_session_cache, and I ignored it.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,272772,272783#msg-272783
___
nginx mailing list
nginx@nginx.org
http://mailman.ngi
Hi, Alexks,
I try your proposal and it doesn't work. Actually my issue is the same as this
one
http://stackoverflow.com/questions/5100971/nginx-and-proxy-pass-send-connection-close-headers.
1. I add "keeplive_request 0". The result is that the "Connection: close"
header is sent to client for e
Hello,
I have run an application behind a nginx reverse proxy and I can't make it to
work
a) if I access this application using https://1.1.1.1:443 it works (certificate
warning)b) if I access this application using https://myapp.mydomain.org, I get
access to the login page location ^~ / {
So I figured out the problem is a bit of a dynamic one.
My Nginx accepts some connections via cloudflare's proxy and other's via
their DNS only and other connections go through a load balancing ip that
sets a x-forwarded-for header containing the real IP, While others can avoid
all of that and con
Hello!
On Sun, Mar 05, 2017 at 09:58:47PM -0500, Nomad Worker wrote:
> I read the code of ssl module, the directive ssl_session_timeout seems only
> used for ssl session cache, not for ssl session ticket.
> the document describes the directive as 'Specifies a time during which a
> client may re
Again, it is not empty, nor containing an hyphen...
Look slowly to the log line and compare it to the log format. You use
hyphens as separators, which, again, might not be a good idea at this
precise location.
The IP address you get is a private one though, so not 'client' but rather
'downstream'
Nomad Worker:
I read the code of ssl module, the directive ssl_session_timeout seems only
used for ssl session cache, not for ssl session ticket.
the document describes the directive as 'Specifies a time during which a
client may reuse the session parameters.' Is it not exactly?
Is there any ti
