Only time you see a log for a web socket connection is when it get
disconnected. So you will not see a log when it connects, transfer data
over it.
On Mon, Jan 11, 2016 at 8:21 PM, tammini
wrote:
> Does that mean once a websocket connection is opened successfully, any
> subsequent requests sent
Does that mean once a websocket connection is opened successfully, any
subsequent requests sent on that connection cannot be logged ?
Thanks.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,263878,263938#msg-263938
___
nginx mailing list
ngi
Dear Maxim Dounin
Hello !
Thank you for quick response.
I understand your answer.
Add
if ($ssl_client_i_dn != "...") {
return 403;
}
and I can limit access from issued intermediate CA.
Regards,
Atsushi
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,263895,263936#msg-263936
I am facing the same issue on my Debian 7 Server. I downgraded to
1.0.1e-2+deb7u12 version of libssl1.0.0 and restarted nginx but the issue is
still occurring for me. I can still see the same logs.
I also tried following these instructions(installed the deb packages made by
these instructions) but
Hi Lukas,
On Sun, Jan 10, 2016 at 11:05 AM Lukas wrote:
> I found that recommendation. Since I also read that it would not be
> fully compatible with OWASP/CRS I have not given it a try.
>
> What is the situation regrading OWASP/CRS?
>
Currently there are three different versions of ModSecurit
