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

Go Issues Packages

golang.org/x/net/websocket

unclear whether Conn.Read documentation refers to frame or messageDocumentationNeedsInvestigation

#71107 opened 5 months ago by fortuna

1

hangs when connecting to a plain TCP socket NeedsInvestigation

#58630 opened 2 years ago by jurisbu

0

unrecognized failuresNeedsInvestigation

#58180 opened 2 years ago by gopherbot

1

implement support for websockets over HTTP/2Proposal

#53209 opened 3 years ago by ethanpailes

4

override the Host headerNeedsInvestigation

#33307 opened 6 years ago by fuglede

2

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

#32866 opened 6 years ago by msoedov

4

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

#31849 opened 6 years ago by mei-rune

0

Read() doesn't read the whole frameNeedsInvestigation

#27967 opened 6 years ago by antong

3

add a web socket client when targeting js/wasmFeatureRequestNeedsInvestigationOS-JS

#27311 opened 6 years ago by definitelycarter

2

remedy neglect; merge with gorilla websocket?NeedsDecision

#18152 opened 8 years ago by zombiezen

64

fails to Receive a single frame sent in chunks from BrowserNeedsInvestigation

#16945 opened 8 years ago by mattbaird

6

Naming of TLSConfigNeedsInvestigation

#16447 opened 9 years ago by evrimoztamur

6

ErrBadStatus should include the bad status codeNeedsInvestigation

#13528 opened 9 years ago by noahlt

1

Asymmetric treatment of OriginNeedsInvestigation

#12426 opened 9 years ago by anacrolix

0

TestClose fails on Plan 9OS-Plan9Testing

#11454 opened 10 years ago by mikioh

1

messages not exposed in package APINeedsInvestigation

#7632 opened 11 years ago by gopherbot

5