CODEWITHSUNDEEP
google-chromeinternet-explorerlocalhostburp
mimo
mimo

Reputation: 6817

Burp Interception does not work for localhost in Chrome

I can't intercept requests made by Chrome version 73.0.3683.86 to my localhost site.

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.

Also under "Proxy" > "HTTP History" there is only request to external sites, and all requests to http://127.0.0.3:80 are not recorded.

When I reload same page by Internet Explorer 11, initial GET request is intercepted by Burp, as expected. Also "Proxy" > "HTTP History" shows all the requests to local site http://127.0.0.3:80

What is the problem with the Chrome? Thanks!

Upvotes: 4

Views: 12383

Answers (8)

Bakhtyar Jaff
Bakhtyar Jaff

Reputation: 1

there is many ways to proxy capture localhost ,try this on terminal

ifconfig | grep "inet " it will give your private ip address and like(000.00.000.00) and you have to add (80)port and it become (000.00.000.00:80) so test in any browser that will be captured.

Upvotes: 0

Илья Хоришко
Илья Хоришко

Reputation: 1195

It helped me

I turned on this settings enter image description here

Upvotes: 0

Vicky Malhotra
Vicky Malhotra

Reputation: 360

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! Example: 1]

Upvotes: 0

soffie
soffie

Reputation: 1

You have to subtract the implicit bypass rules defined in Chrome (https://chromium.googlesource.com/chromium/src/+/master/net/docs/proxy.md#Implicit-bypass-rules)

Requests to certain hosts will not be sent through a proxy, and will instead be sent directly.

We call these the implicit bypass rules. The implicit bypass rules match URLs whose host portion is either a localhost name or a link-local IP literal. Essentially it matches:

localhost

*.localhost [::1]

127.0.0.1/8

169.254/16

[FE80::]/10

https://chromium.googlesource.com/chromium/src/+/master/net/docs/proxy.md#Bypass-rule_Subtract-implicit-rules

Whereas regular bypass rules instruct the browser about URLs that should not use the proxy, Subtract Implicit Rules has the opposite effect and tells the browser to instead use the proxy.

In order to be able to proxy through the loopback interface, you have to add the entry

<-loopback>

in the list of hosts for which you don't want to a proxy. It is a bit confusing, indeed.

Upvotes: 0

mohan srirama krishna P
mohan srirama krishna P

Reputation: 43

You can solve this problem by adding an entry in /etc/hosts file like below

127.0.0.1   localhost   
127.0.0.1   somehostname

Now burp will intercept request from somehostname

Upvotes: 2

Bryan Burman
Bryan Burman

Reputation: 1

I experienced the same issue when I upgraded from Opera 58.0 to 60.0. I think that this is Chrome related, because I've also experienced it in all other Chrome browsers. Opera 58 utilizes Chrome 71.0.3578.98. Opera 60 utilizes version Chrome 73.0.3683.103. Something was definitely updated in Chrome between these versions to cause this problem to happen.

Upvotes: 0

jaxmeier
jaxmeier

Reputation: 509

Found the solution late yesterday. I am using the Chrome extension ProxySwitchy, but it doesn't matter if you use that or the system proxy configuration. The solution works the same way.

Chrome ProxySwitchy Extension

Windows 10 Proxy Settings

Upvotes: 12

PortSwigger
PortSwigger

Reputation: 277

Which version of Chrome are you using?

Have you tried using the FoxyProxy Chrome extension?

As a workaround, you could modify the hosts file on your machine.

Upvotes: 0

Related Questions