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
the proxify tool uses fake-http (simplehttpserver) combined with dns hijacking (tinydns custom resolver) to transparently TLS-MITM connections in order to replay them in burp avoiding sending the traffic again.
We can reuse the same mechanism to serve to headless chrome the already crawled http raw response with much higher speed via standard library, then the headless engine will do the heavy work of rendering the raw HTML and pulling any third party file necessary not yet crawled.
This approach might have multiple benefits:
Works with more websites using weak ciphers (ztls) as the browser reuse the data already crawled
The speed of standard library is much higher, and hopefully the chrome engine for single pages might match same speed as no more network activity out of loopback interface is needed
The text was updated successfully, but these errors were encountered:
Please describe your feature request:
the proxify tool uses fake-http (simplehttpserver) combined with dns hijacking (tinydns custom resolver) to transparently TLS-MITM connections in order to replay them in burp avoiding sending the traffic again.
We can reuse the same mechanism to serve to headless chrome the already crawled http raw response with much higher speed via standard library, then the headless engine will do the heavy work of rendering the raw HTML and pulling any third party file necessary not yet crawled.
This approach might have multiple benefits:
The text was updated successfully, but these errors were encountered: