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
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
> 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
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
> 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.
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
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
Hi.
The client can't load the image served by nginx-1.13.6+.
[App with Android 7.1.2 4.4.4 4.12 series]
It works well in nginx-1.13.5, but go wrong in ngnx-1.13.6+.
The change is http://hg.nginx.org/nginx/rev/12cadc4669a7.
I found the similar problem.
BTW. It works well by the temporary fix.
--- a/src/http/v2/ngx_http_v2_filter_module.c
+++ b/src/http/v2/ngx_http_v2_filter_module.c
@@ -446,7 +446,6 @@ ngx_http_v2_header_filter(ngx_http_request_t *r)
if (h2c->table_update) {
ngx_log_debug0(NGX_LOG_DEBUG_HTTP, fc->log, 0,
Hello!
There is a known issue caused by some obsolete client like old version
okhttp (incomplete protocol implements).
Here is the ticket: https://trac.nginx.org/nginx/ticket/1397.
___
nginx-devel mailing list
nginx-devel@nginx.org
On Sun, Jul 08, 2018 at 11:36:45PM -0700, Ian Gudger wrote:
> Any update on this?
The original idea with SIGIO is to wake up master process from
sigsuspend() when the message channel is ready for I/O. This
feature is currently de-facto unused because if message writing
fails, the message is lost
Hello!
On Wed, Jul 11, 2018 at 08:56:56PM +0800, 洪志道 wrote:
> But there are still some clients use the old version.
> Is it a way to be compatible with it?
> Or other suggestions?
> @Maxim Dounin
As I already wrote in ticket #1397, we can try introducing a
workaround in nginx, but I'm not
Get it, I'll try it, thank you again.
On Thu, Jul 12, 2018 at 1:02 AM Maxim Dounin wrote:
> Hello!
>
> On Wed, Jul 11, 2018 at 08:56:56PM +0800, 洪志道 wrote:
>
> > But there are still some clients use the old version.
> > Is it a way to be compatible with it?
> > Or other suggestions?
> > @Maxim
Thank you.
But there are still some clients use the old version.
Is it a way to be compatible with it?
Or other suggestions?
@Maxim Dounin
On Wed, Jul 11, 2018 at 5:43 PM tokers wrote:
> Hello!
>
> There is a known issue caused by some obsolete client like old version
> okhttp (incomplete
14 matches
Mail list logo
