Closed abhilashaman08 closed 1 year ago
@basil00 could you help?
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!
On Tue, 24 Jan 2023 at 6:50 AM, basil00 @.***> wrote:
Closed #327 https://github.com/basil00/Divert/issues/327 as completed.
— Reply to this email directly, view it on GitHub https://github.com/basil00/Divert/issues/327#event-8339757702, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4XWOFXNB46NSONMUPGK77LWT4U6HANCNFSM6AAAAAAUCPIVPY . You are receiving this because you authored the thread.Message ID: @.***>
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: