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

Chromium and Other Browsers Not Working For Specific Host

Eric | Last updated: Jan 20, 2022 04:36PM UTC

I have an issue where Chromium, Chrome, and Edge all give me the same error on an internal website that I need to test. The specific error is below. "Hmmm… can't reach this page It looks like the webpage at [redacted] might be having issues, or it may have moved permanently to a new web address. ERR_HTTP2_PROTOCOL_ERROR" The site does not have a valid SSL certificate, so browsing to it normally requires me to ignore that error and proceed. I can view the site fine in any browser (except chromium) but as soon as I try to send traffic through burp I receive the above error, but ONLY for this internal site. Any other site works fine. Other internal sites also work fine. If I capture the initial request to view the site and send it to the repeater and then send the request from there I get a 200 response and can see the html of the page. If I copy that response to view in browser I receive the same error as above again. For some reason this WILL work in internet explorer 20h2, but the site does not render properly and interfaces I need to work with are missing. Any ideas? I do have burp's CA certificate installed. I am using burp professional.

Eric | Last updated: Jan 20, 2022 06:48PM UTC

FYI the solution was found, for anyone searching, the repeater seems to default to http/1 while the default proxy listener uses http/2. Editing the listener to remove support for http/2 fixes the issue in this particular instance.

Michelle, PortSwigger Agent | Last updated: Jan 21, 2022 03:20PM UTC