You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ModSecurity-nginx connector is the connection point between nginx and libmodsecurity (ModSecurity v3). Said another way, this project provides a communication channel between nginx and libmodsecurity. This connector is required to use LibModSecurity with nginx.
8
+
The ModSecurity-nginx connector is the connection point between nginx and libmodsecurity (ModSecurity v3). Said another way, this project provides a communication channel between nginx and libmodsecurity. This connector is required to use LibModSecurity with nginx.
9
9
10
10
The ModSecurity-nginx connector takes the form of an nginx module. The module simply serves as a layer of communication between nginx and ModSecurity.
11
11
@@ -176,6 +176,17 @@ using the same unique identificator.
176
176
177
177
String can contain variables.
178
178
179
+
modsecurity_proxy_protocol_ip
180
+
-----------
181
+
**syntax:***modsecurity_proxy_protocol_ip on | off*
182
+
183
+
**context:***http, server, location*
184
+
185
+
**default:***off*
186
+
187
+
If activated, ModSecurity logs the actual IP address of a client when the connections is proxied using the Proxy Protocol.
188
+
If a connection is proxied without this directive activated, the logged IP address is the one of the proxy server.
If you are facing problems getting your added functionality to pass all the nginx tests, feel free to contact us or the nginx mailing list at: http://nginx.org/en/support.html
228
239
229
-
### Debugging
240
+
### Debugging
230
241
231
242
We respect the nginx debugging schema. By using the configuration option
232
243
"--with-debug" during the nginx configuration you will also be enabling the
0 commit comments