[GH-ISSUE #1331] Authentication not available for Websocket #433

New issue

Closed

opened 2026-03-16 15:18:13 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 15:18:13 +03:00

Owner

Originally created by @arpanbag001 on GitHub (Nov 17, 2020).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1331

Describe the bug
Feature to authenticate Websocket connection is missing, even though the Readme file says Basic and Bearer authentications are available for Websocket.

To Reproduce
Steps to reproduce the behavior:

Go to Realtime page
Go to "Websocket" tab
Can't find any section to use authentication or to add custom headers.

Expected behavior
In the Websocket tab, there should be a section to add authentication and also maybe custom headers, like the section available in Home page.

Screenshots

Faced on:
Windows 10, with PWA
Browsers: Chrome, Firefox
Hopscotch v1.9.9

Originally created by @arpanbag001 on GitHub (Nov 17, 2020). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1331 **Describe the bug** Feature to authenticate Websocket connection is missing, even though the Readme file says Basic and Bearer authentications are available for Websocket. **To Reproduce** Steps to reproduce the behavior: 1. Go to Realtime page 2. Go to "Websocket" tab 3. Can't find any section to use authentication or to add custom headers. **Expected behavior** In the Websocket tab, there should be a section to add authentication and also maybe custom headers, like the section available in Home page. **Screenshots** ![image](https://user-images.githubusercontent.com/10957940/99366631-dff29580-28de-11eb-9bae-d93a33e4e744.png) Faced on: Windows 10, with PWA Browsers: Chrome, Firefox Hopscotch v1.9.9

kerem closed this issue

2026-03-16 15:18:19 +03:00

kerem commented

2026-03-16 15:18:25 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 17, 2020):

https://devcenter.heroku.com/articles/websocket-security#:~:text=The%20WebSocket%20protocol%20doesn't,also%20secure%20the%20WebSocket%20connection.

https://stackoverflow.com/questions/4361173/http-headers-in-websockets-client-api

WebSocket doesn't support custom headers nor Authorization.

Even though you can use Basic Auth (deprecated) in WebSocket URL input.

Ex:

ws://username:password@example.com

@liyasthomas commented on GitHub (Nov 17, 2020): https://devcenter.heroku.com/articles/websocket-security#:~:text=The%20WebSocket%20protocol%20doesn't,also%20secure%20the%20WebSocket%20connection. https://stackoverflow.com/questions/4361173/http-headers-in-websockets-client-api WebSocket doesn't support custom headers nor Authorization. Even though you can use Basic Auth (deprecated) in WebSocket URL input. Ex: ``` ws://username:password@example.com ```