golang.org/x/net/websocket - Go Issues

Go Issues Packages

golang.org/x/net/websocket

hangs when connecting to a plain TCP socket NeedsInvestigation

#58630 opened 1 month ago by jurisbu

0

unrecognized failuresNeedsInvestigation

#58180 opened 2 months ago by gopherbot

1

add Config.DialContextProposal

#57953 opened 2 months ago by Cyberax

1

implement support for websockets over HTTP/2Proposal

#53209 opened 10 months ago by ethanpailes

3

override the Host headerNeedsInvestigation

#33307 opened 3 years ago by fuglede

2

add runnable versions of examples mentioned in Server.Handshake documentationDocumentationNeedsFixhelp wanted

#32866 opened 3 years ago by msoedov

3

add ability to replace Dialer with DialContext in the Config struct, like http.TransportNeedsInvestigation

#31849 opened 3 years ago by mei-rune

0

Read() doesn't read the whole frameNeedsInvestigation

#27967 opened 4 years ago by antong

3

add a web socket client when targeting js/wasmFeatureRequestNeedsInvestigation

#27311 opened 4 years ago by definitelycarter

2

remedy neglect; merge with gorilla websocket?NeedsDecision

#18152 opened 6 years ago by zombiezen

57

fails to Receive a single frame sent in chunks from BrowserNeedsInvestigation

#16945 opened 6 years ago by mattbaird

6

Naming of TLSConfig

#16447 opened 6 years ago by evrimoztamur

6

ErrBadStatus should include the bad status code

#13528 opened 7 years ago by noahlt

1

Asymmetric treatment of Origin

#12426 opened 7 years ago by anacrolix

0

TestClose fails on Plan 9OS-Plan9Testing

#11454 opened 7 years ago by mikioh

1

messages not exposed in package API

#7632 opened 9 years ago by gopherbot

5