> Since you are using newer openssl, you may want to apply this patch
I agree, many thanks to Piotr Sikora and to you, Frank!
2nd patch applied as well.
My error log is a lot more readable now. I can see those real critical
messages without being cluttered by meaningless/unfixable SSL issues.
Glad it works and thanks Piotr Sikora for the patch!
Since you are using newer openssl, you may want to apply this patch:
https://nginx.googlesource.com/nginx/+/ec0b8aad6ca3cb37e03d1c06e42f110e4737af1f%5E%21/
On Wed, Jul 11, 2018 at 6:18 AM, shiz wrote:
> > Those unsupported ssl version messag
So my issue is mostly directed towards Yichun Zhang (agentzh) if he is still
active here. I hope so.
My problem is I am trying to increase my Cache HIT ratio by removing
arguments from the URL that are fake / unwanted and order the arguments in a
alphabetical (same order every time) for a higher
Hello, Scott.
I think, you can try $request_length.
Here is a convenient link to help you with your task:
http://nginx.org/en/docs/varindex.html
Most of times you can find a proper variable there.
On 11.07.2018 16:53, Callum Scott wrote:
I'm currently looking at swapping out some of our Apache
I'm currently looking at swapping out some of our Apache web servers for
Nginx to act as a reverse proxy.
One of my issues is that I need, at least in the short term, for the log
format to remain the same.
I have two issues that are cropping up.
The first is that with my current configuration I
> Those unsupported ssl version messages should be in "info" level
That is a very useful patch, many thanks Frank
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,280446,280496#msg-280496
___
nginx mailing list
nginx@nginx.org
http://mailman
Hello,
I have the following config
Frontend (with IP x.y.1.1) -> Proxy
In the Proxy settings I have "allow x.y.1.1" and this work very well.
Now I want to see the client IP how access to frontend in the proxy logs
and have add something like
# to get real IP who access
set_real_ip_from x.y.1.1/3
