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
Can ModSecurity monitor and block websocket traffic?
(Might be the same question as #831 But that one's not totally clear to me and maybe things have changed since then.)
My current setup: An AngularJS/AngularSails web application "talks" with an NodeJS/SailsJS backend solely over websocket (resp. the Sails implementation of socket.io). In between sits nginx as a proxy, configured like so:
I would say no as websockets are data streams and you can't intercept stream blocks to analyze, it would probably take a huge restructuration and creating new stages.
Can ModSecurity monitor and block websocket traffic?
(Might be the same question as #831 But that one's not totally clear to me and maybe things have changed since then.)
My current setup: An AngularJS/AngularSails web application "talks" with an NodeJS/SailsJS backend solely over websocket (resp. the Sails implementation of socket.io). In between sits nginx as a proxy, configured like so:
Can I use ModSecurity in nginx to monitor, analyse, and block the traffic going over this websocket connection? If so: How?
The text was updated successfully, but these errors were encountered: