imroc / imroc/req

Hijack H1 Connection (e.g. for using as Websocket)

Open
#305 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement modified-stdlib priority:low
Dominant language
Go
Stars
4.9k
Forks
409
Avg merge
6h 47m
Merged PRs (30d)
7

Description

I think all that would be needed is that the persistConn gets "removed". E.g. decConnsPerHost would have to be called I think, maybe more?

I think the http.Hijacker interface could be implemented for this?

Is there currently any way to establish a WS Connection using imroc/req?

Thank you!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how persistConn is managed and where decConnsPerHost is called when a connection leaves the pool. Review Go's http.Hijacker interface and determine the entry point needed for req to establish a WebSocket connection. Done means the requested hijacking behavior is defined and verified without retaining the connection in the HTTP pool.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.