Research Academy
My account Customers About Blog Careers Legal Contact Resellers
The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

Burp Interception does not work for localhost in Chrome

Milan | Last updated: Apr 10, 2019 04:00PM UTC

I can't intercept requests made by Chrome to my localhost site. - Local host site is running on IIS on http://127.0.0.3:80 - Burp proxy lister is default one on 127.0.0.1:8080 - Interception rules are default one as well When Interception is turned ON and I reload page in Chrome browser, no request is "caught" by Burp, my local site loads and only the external requests are intercepted, such as loading external scripts from CDN. When I reload same page by Internet Explorer 11, initial GET request is intercepted by Burp, as expected. Any idea what is the problem with the Chrome? Thanks!

Burp User | Last updated: Apr 10, 2019 04:03PM UTC

For Chrome under "Proxy" > "HTTP History" there is only request to external sites, and all requests to http://127.0.0.3:80 are not recorded. For Internet Explorer "Proxy" > "HTTP History" shows all the requests to local site http://127.0.0.3:80

Liam, PortSwigger Agent | Last updated: Apr 11, 2019 10:53AM UTC

Milan, this seems to be an issue with the latest version of Chrome. You could try editing the hosts file on your system. Alternatively, you'll need to use another browser. Please let us know if you need any further assistance.

Burp User | Last updated: Jul 11, 2019 04:40AM UTC

This also happens in Firefox.

Rose, PortSwigger Agent | Last updated: Jul 11, 2019 01:15PM UTC

Ira, thanks for letting us know. Is that the latest version of Firefox?

Liam, PortSwigger Agent | Last updated: Jul 11, 2019 01:16PM UTC

Thanks for the update Andrew.

Burp User | Last updated: Jul 14, 2019 12:36PM UTC

Try one of these: 1. (for firefox) go to about:config and change network.proxy.allow_hijacking_localhost to true 2. try http://127.0.0.3.:80 instead of http://127.0.0.3:80 (dot added after IP address)

Liam, PortSwigger Agent | Last updated: Jul 16, 2019 10:44AM UTC

John, which browser are you using?

Burp User | Last updated: Jul 22, 2019 01:42PM UTC

Thank you! This setting solved the problem (in firefox) - network.proxy.allow_hijacking_localhost to true

Burp User | Last updated: Aug 05, 2019 06:28AM UTC

Thanks Andrew... it worked

Burp User | Last updated: Aug 07, 2019 07:43PM UTC

Thanks Andrew! it is working now.

Burp User | Last updated: Oct 23, 2019 06:38AM UTC

thanks ...after the updation i was confused why burp not working

Burp User | Last updated: Nov 11, 2019 12:34AM UTC

After changing setting network.proxy.allow_hijacking_localhost to true, localhost now throws 403 Forbidden.

Burp User | Last updated: Nov 21, 2019 01:03PM UTC

I have the same problem but cannot switch to another browser. Is there any way to configure Chrome or Burp to work together for local servers?

Ben, PortSwigger Agent | Last updated: Nov 21, 2019 01:14PM UTC

Hi Hendrik, Have you tried the workaround here: https://stackoverflow.com/questions/55616614/burp-interception-does-not-work-for-localhost-in-chrome/55850268#55850268 "When the instructions tell you to clear the exceptions, enter <-loopback> as the sole entry and save." Please let us know if this solves your issue.

Burp User | Last updated: Feb 01, 2020 01:38AM UTC

Thanks Andrew! This setting solved the problem (in firefox) - network.proxy.allow_hijacking_localhost to true..you save lots of time

ravitej | Last updated: Apr 11, 2020 03:12AM UTC

lets connect tomm.. poi tinu

Xeek3y | Last updated: May 15, 2020 02:53PM UTC

Make sure you haven't enabled socks proxy option, it happened with me too and i found the solution when i disabled the socks proxy option, just make sure it's disabled!

Nikhil | Last updated: Mar 13, 2021 06:48PM UTC

Hi Ben What you said will work in Windows, but in Kali Linux using google chrome, it is not allowed to change proxy settings. How to resolve the issue then ? Is there any way of adding <-loopback> by terminal?

Ben, PortSwigger Agent | Last updated: Mar 15, 2021 11:04AM UTC

Hi Nikhil, Have you tried some of the suggestions in the following post: https://superuser.com/questions/1418848/how-to-avoid-google-chrome-proxy-bypass-for-localhost

Nikhil | Last updated: Mar 16, 2021 09:34PM UTC

Yes I did, but not much success. I executed below command but still Chrome + Burp Suite combo is unable to work when visting localhost based sites google-chrome --proxy-server="127.0.0.1:8090" --proxy-bypass-list="<-loopback>"

Sanjay | Last updated: Jun 16, 2021 04:27AM UTC

I was facing the same problem in chrome(90.0.4430.93). Add a new entry in /etc/hosts file with a new name pointing to 127.0.0.1. 127.0.0.1 localhost 127.0.0.1 somehostname Use somehostname instead of localhost. Ref: https://stackoverflow.com/questions/55616614/burp-interception-does-not-work-for-localhost-in-chrome/55850268#55850268

sido | Last updated: Feb 27, 2022 03:52PM UTC