The problem of speed when working via WAF
Published 3 months ago
Published 3 months ago
sark888
Updated 3 months ago
0
When working in reverse proxy mode, the speed is cut, and when working with nginx without waf, the speed is limited by the width of the internet channel. When working with waf and running streaming services such as Emby, the speed drops by dozens of times, reaching no more than 1 Mbit. The default settings of WAF. How can I configure the settings so that the streaming services work correctly and WAF does not check their traffic? In general, when working with your WAF, the speed is limited to no more than 1 Mbit, which is not the case with competitors.
Carrie
Updated 3 months ago
As long as the traffic is HTTP/HTTPS, the WAF will default to inspect it; other traffic is passed through. If you don’t want streaming media to be detected or rate-limited by the WAF, the most reasonable approach is to bypass the WAF for that traffic.
Carrie
Updated 3 months ago
If your streaming traffic can be splited, bypassing can be achieved by making DNS not resolve to the WAF; but if it cannot, there isn’t a solution right now.
sark888
Updated 3 months ago
0
I disabled traffic checking, changed the mode to audit (monitoring), but it didn't help.
Carrie
Updated 3 months ago
Audit Mode will also detect traffic; it just won’t block the attack behavior.
sark888
Updated 3 months ago
0
<@1282641039298924606> How is it possible to split traffic in the CE version? I haven't found a way to specify a specific location in reverse proxy mode out of the box