A TCP Proxifier Log Can Miss the Browser’s QUIC Traffic
Inspect UDP separately when a Proxifier setup captures TCP while the browser uses HTTP/3.
A browser can use HTTP/3 over QUIC while a Proxifier setup intercepts TCP connections. A TCP connection log is then an incomplete view of that browser’s outward traffic.
First establish whether the differing request used UDP. Proxifier’s Windows changelog records UDP logging and blocking support from version 4.11, alongside its TCP proxying capabilities. Inspect the options and recorded transport for the actual installed build.
Blocking a datagram is different from carrying it through a proxy. A browser may fall back to a supported TCP transport when QUIC is unavailable; that outcome does not establish an HTTP/3 proxy path.
Keep native browser proxy selection separate from process-level interception. A browser explicitly configured with an HTTP proxy is another arrangement from an otherwise direct browser whose TCP sockets are being intercepted. Identify which arrangement produced the observation before changing unrelated proxy settings.