hoppscotch/hoppscotch-extension

[feature]: Websocket support on the extension

Open

#303 opened on May 16, 2023

View on GitHub
 (5 comments) (3 reactions) (1 assignee)TypeScript (145 forks)auto 404
CodeDaygood first issue

Repository metrics

Stars
 (289 stars)
PR merge metrics
 (PR metrics pending)

Description

Is there an existing issue for this?

  • I have searched the existing issues

Summary

If available, websocket connections should be redirected through the browser extension, just like HTTP ones.

This has been already suggested in hoppscotch/hoppscotch#2194 but the issue was closed by the author as completed, even though it's not completed.

Why should this be worked on?

Because developing websockets is almost impossible else, since HTTPS pages can only connect to wss sockets, and in development TLS is usually skipped

Contributor guide

Research direction
Examine the existing HTTP proxy implementation in the extension and extend it to handle WebSocket connections. Research how to intercept WebSocket upgrade requests using browser extension APIs like chrome.webRequest or chrome.debugger.
Tech stack
typescript
Domain
networkingweb dev
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptBrowser extension developmentWebSocket protocol
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40