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

SSL SNI not used with upstream proxy

Ron | Last updated: Sep 21, 2016 07:08PM UTC

Hello, SSL SNI works properly on regular connections but not on connections through upstream http proxy. After getting Handshake_Failure alerts when using an upstream http proxy I've confirmed that the "Server_Name" extension is missing for SSL handshakes when an upstream proxy is enabled. Could you please confirm if it is a bug or should I check anything else? Details: Windows 10 Burp Pro v1.7.06 using the BurpSuitePro.exe executable JRE 8 Universal JCE installed

PortSwigger Agent | Last updated: Sep 22, 2016 09:43AM UTC

We have this issue captured in our backlog of work, and will update this thread when we have some progress to report, thanks.

Burp User | Last updated: Apr 03, 2017 04:09PM UTC

Hello, I am afraid I am having the same issue with Burp Suite Pro 1.7.19... The SNI is correctly sent if I disable the upstream proxy, but it is missing from the Client Hello when I enable the upstream proxy (squid). Toggling the setting "disable java SNI extension" (and restarting) do not fix this. Could you please investigate? Windows 7 x64 With Burp installer or .jar Java : 1.8.0_121-b13 JCE installed

Burp User | Last updated: Apr 07, 2017 12:41AM UTC

I need this too, damn...

PortSwigger Agent | Last updated: Apr 07, 2017 08:01AM UTC

Just to let you know that the latest release (1.7.24) fixes the SNI problem with upstream proxies. Thanks again for your feedback, and let us know if you run into any other issues.

Burp User | Last updated: May 26, 2017 12:53PM UTC