Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Error "No response received from remote server." yields status 200

Reinier | Last updated: Jun 12, 2018 04:43PM UTC

Situation: - configured upstream proxy - proxy is not reachable (not connected to the network) - request arbitrary website (firefox, burp as proxy) - Burp responds with `Error No response received from remote server.`, but the status-code is 200 Expected behavior would be a status-code 503 (Service unavailable). Version is Burp Professional v1.7.33

Liam, PortSwigger Agent | Last updated: Jun 13, 2018 09:17AM UTC

We use to the status 200 code to ensure that the browser doesn't display it's own error message.

Burp User | Last updated: Jul 12, 2018 03:33PM UTC

As an api/web developer I'd say thats one terrible argument to - break http compliance - break all automation around burp (relying OK status codes) - break common sense predictability Further, I cannot think of any browser not showing a 503 webpage that includes a body, like burp does. I would vote for this change because it helps integrating burp with CI tools. Must be an appealing area for Portswigger to improve support in.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.