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
Windivert (webfilter) Blacklist not working in Chrome. Works well in Edge Firefox. Packets are captured well, but seems like TCP RST does not reset connection. Following snippet:
The webfilter example is not very useful. It only supports HTTP/1.1, which was somewhat relevant in 2011 when it was first written, but is no longer relevant as almost all websites/browsers use encryption + more modern web protocols. This sample should be retired.
As for your code, this does not appear to be webfiter anyway, so I cannot comment.
Thanks for your reply.
Actually what we do is we hijack the packet through Windivert on tcp.port
443,outbound and find url from its payload, once url is found, we match
them with our internal category matching criteria, and blocks them if its
on matching criteria. But in chrome, we saw some packets were not being
captured. Is there a way to insure all packets at this port is captured?
Since you marked the thread as closed,
Can you reply here?
Thanks again for your help!
Windivert (webfilter) Blacklist not working in Chrome. Works well in Edge Firefox. Packets are captured well, but seems like TCP RST does not reset connection. Following snippet:
The text was updated successfully, but these errors were encountered: