To top it all off, we have updated the WFP and TDI drivers, and as per our tradition, we have also updated CoreLibs, DnsLibs, and scriptlets to ensure even more stable operation. Also, when the internet connection was unstable, the application could behave unpredictably or even crash. Previously, the application would crash in some cases due to high memory usage. To enable HTTP/3 filtering, go to Settings → Advanced Settings → Filter HTTP/3.Īside from HTTP/3 filtering, we have made several improvements to boost the overall performance of AdGuard for Windows. However, you can still use this feature in Edge and Firefox browsers for testing and debugging purposes. Please note that Chrome does not currently support HTTP/3 filtering due to its own method of verifying QUIC and TCP certificates, which does not recognize AdGuard certificates. You can learn more about the advantages of this feature in our blog. HTTP/3 filtering, powered by our latest CoreLibs v1.12, uses the QUIC network protocol instead of the TCP transport layer protocol, providing increased privacy and security. And now we are pleased to introduce AdGuard v7.15 for Windows, also equipped with this feature. Just recently, we released AdGuard v2.12 for Mac, with its main feature being the brand-new HTTP/3 filtering. At AdGuard, it is the season of HTTP/3 filtering.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |