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

What should be simple websockets lab help

Aar0n | Last updated: Apr 05, 2020 10:43AM UTC

Hi all, I have the same issue with all three websockets labs. When I navigate to (for example) https://ac...e0000.web-security-academy.net/chat directly (ie not through burpsuite) I get the 'CONNECTED: -- Now chatting with Hal Pline --' and am able to interact with 'Hal Pline' as I would expect. When I navigate to the same page through burpsuite there is no 'CONNECTED: -- Now chatting with Hal Pline --' message, the 'Send' button appeasrs to have no functionality. Nothing appears in the Websockets history tab. Nothing happens. (Requests are being intercepted as expected as the chat page loads (i.e. burpsuite and firefox's proxy/connection settings are the same: 127.0.0.1 port: 8080) I assume this is something simple that I am unaware of. Can anybody help me figure out what it is? (Or just tell me if the educational value in troubleshooting it is worth less than the hassle of fixing whatever the simple issue I am just blind to is!) Thanks in advance for any help! These tutorials are great during lockdown!

Hannah, PortSwigger Agent | Last updated: Apr 06, 2020 08:30AM UTC

In your browser proxy configuration, could you try removing the SOCKS host proxy configuration, and leave it blank?

Aar0n | Last updated: Apr 08, 2020 09:34PM UTC

Hi Hannah, thanks for the reply. Yes that worked! Great stuff I appreciate your help with this (and the academy generally) All the best, Aaron

Aar0n | Last updated: Apr 08, 2020 09:34PM UTC

Hi Hannah, thanks for the reply. Yes that worked! Great stuff I appreciate your help with this (and the academy generally) All the best, Aaron

Aar0n | Last updated: Apr 09, 2020 06:20AM UTC

Not sure why I double posted my last reply. Anyway I just wanted to add that although I haven't looked into it as yet, I assume socks proxy utilises websockets (hence the name) and was hijacking the websocket connection in one way or another. Anyway, thanks again.

Hannah, PortSwigger Agent | Last updated: Apr 09, 2020 07:00AM UTC