Телеграмм чат группы nginx

Size: a a a

nginx_ru

2021 April 07

If I place the access_log at the server block, then even though I declare such location blocks with access_log off and log_not_found off it logs them anyway

источник

22:05пожаловаться #1

Hugo Florentino in nginx_ru

So the problem is error_pages then when used in a default server block?
The documentation doesn't mention this anywhere

источник

22:08пожаловаться #2

Anton Noginov in nginx_ru

The documentation states that definitely: http://nginx.org/en/docs/http/ngx_http_log_module.html

Requests are logged in the context of a location where processing ends. It may be different from the original location, if an internal redirect happens during request processing.

If you want to skip stuff like robots.txt - just define a separate location for them.
But that's weird - you want to log all the requests to unknown host, and http://ip/robots.txt kinda one of.

источник

22:11пожаловаться #3

Hugo Florentino in nginx_ru

So nginx doesn't have a way then to catch requests as they are before redirecting to custom error pages ?

источник

22:13пожаловаться #4

Hugo Florentino in nginx_ru

The directive access_log then is a bit crippled

источник

22:15пожаловаться #5

Anton Noginov in nginx_ru

That makes no sense indeed. As prior to internal redirect you don't have let's say status code defined - it might be amended withing further processing.
As well as response itself.

источник

22:16пожаловаться #6

Anton Noginov in nginx_ru

You may however do a wrapper there - either logging with lua, or using let's say auth_request to log

Number of ways.

источник

22:17пожаловаться #7

Hugo Florentino in nginx_ru

If you have a reverse proxy, you might want to capture all requests exactly as they come for auditing purposes. The destination is irrelevant in that scenario.

источник

22:17пожаловаться #8

Lilo Stich in nginx_ru

Что тут происходит? Можно вклинуться?

Hi, guys.

I have 2 Nginxs here.
One is Stream on 443 with proxy_protocol enabled.
And second is HTTP with SSL termination.
Whole day tried to log the IP of clients, bliad.

Is this the correct way to log it?

http_x_forwarded_for="$proxy_protocol_addr"

It gaves me my local IP address. Im connect over VPN.

источник

22:17пожаловаться #9

Anton Noginov in nginx_ru

In that case that's ridiculous to intercept errors there. that's dumb indeed.

источник

22:18пожаловаться #10

Hugo Florentino in nginx_ru

OK, I guess I am that dumb, LOL

источник

22:18пожаловаться #11

Hugo Florentino in nginx_ru

the problem again is that lua doesn't log anything because of the redirect

источник

22:19пожаловаться #12

Anton Noginov in nginx_ru

В прокси протоколе же отдается remote_addr

источник

22:19пожаловаться #13

Anton Noginov in nginx_ru

Use other hook.
Mine logs fine whole session :)

источник

22:20пожаловаться #14

Hugo Florentino in nginx_ru

notice the problem is only when placing the access_log witin the location block

источник

22:20пожаловаться #15

Lilo Stich in nginx_ru

Дело в том, что грёбаный 2ой Nginx поднят внутри куб кластера, и если я использую $remote_addr - то получаю какой-то IP из кубовых ендпойнтов - 10.233.76.128.

источник

22:23пожаловаться #16

Lilo Stich in nginx_ru

Видимо IP сервиса кубового, или эндпойнтов

источник

22:24пожаловаться #17

Lilo Stich in nginx_ru

Первый L3 (stream) балансер балансит по NodePort-ам куба.

источник

22:24пожаловаться #18

Anton Noginov in nginx_ru

Ахахаха

Добро пожаловать в волшебный мир cloud native networking.

источник

22:25пожаловаться #19

Lilo Stich in nginx_ru

🥺

источник

22:26пожаловаться #20