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

Burpsuite version v1.7.17

Poonam | Last updated: Feb 13, 2017 09:11AM UTC

I am testing a web application using burp v1.7.17 firstly it was giving me fully qualified dns name error so to resolve it I checked the allow requests to fully qualified dns name checkbox.After that while using upstream proxy I was getting a error that request dropped due to same proxy listener. I tried using other versions like 14,15 and 16 but they were working fine for my site also and also other sites. Thank you

PortSwigger Agent | Last updated: Feb 13, 2017 10:18AM UTC

It sounds like something is wrong with your configuration in Burp and/or your browser. Please revert the DNS-related setting and start Burp up with default project settings. Also restore defaults for user settings (from the Burp menu) in case you have an invalid upstream proxy configuration. Assumimg you haven't changed your browser settings since things were working, this should fix your problem.

Burp User | Last updated: Feb 13, 2017 12:25PM UTC

Hi Dafydd, The settings are same for all the versions I have not changed any of them. I am using Burp pro and burp free edition for proxy chaining. If I'm using any other versions it works fine but only for version 17 I am facing problem.

PortSwigger Agent | Last updated: Feb 13, 2017 01:27PM UTC

Ok thanks, that makes sense. In previous releases, user level preferences were persisted in the Java preferences store. Recently, they were moved to a config file in the user's home directory. Previously, there were separate settings for the free and pro editions, but when the change was made, we inadvertently made Burp use the same file for the free and pro editions. In the next release, we will separate these again. What is happening is that you have configured an upstream proxy rule to point to the other instance of Burp, but that rule is now being picked up by both the free and pro editions, so Burp is forwarding messages back on to itself, hence the error message you observed. The fix for you is to manually remove the upstream proxy rule from the upstream instance of Burp, to prevent the traffic from looping. In the next release of Burp, we'll restore separate persisted settings for the free and pro editions, so you won't need to do this every time.

Burp User | Last updated: Feb 14, 2017 04:29AM UTC