![]() ![]() ![]() The non-proxy-aware client then resolves the domain name to your local IP address, and sends requests directly to your listeners on that interface. To receive the redirected requests, create invisible Burp Proxy listeners on 127.0.0.1:80 and 127.0.0.1:443. Modify your DNS resolution to redirect the relevant hostname, and set up invisible Proxy listeners on the ports used by the application.įor example, if the application uses the domain name, and HTTP and HTTPS on the standard ports, add an entry to your hosts file that redirects the domain name to your local machine: You can force the non-proxy-aware client to connect to Burp. Often, these clients don't support HTTP proxies, or don't provide an easy way to configure them. This is useful if the target application uses a thick client component that runs outside of the browser, or a browser plugin that makes HTTP requests outside of the browser's framework. PROFESSIONAL COMMUNITY Invisible proxyingīurp's support for invisible proxying allows non-proxy-aware clients to connect directly to a Proxy listener.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |