1
86%
main: 86%

Ran 25 Mar 2026 02:10PM UTC

Files 37

Run time 1s

Badge

Embed ▾

Committed 25 Mar 2026 02:05PM UTC coverage: 85.418% (+0.03%) from 85.392%

Job # 23545171746.1

Build Type

push

github

Committed by

web-flow

Commit Message

[FIXED] WebSocket close frame discarding buffered data frames (#2032)

When a NATS server rejects a WebSocket connection (e.g., due to an
expired JWT), it sends a -ERR protocol message followed by a WebSocket
close frame. If both frames arrive in the same TCP read, the
websocketReader.Read() method would process the close frame and
immediately return io.EOF, discarding the -ERR data that had already
been buffered in the pending list.

This caused nats.Connect to return a generic EOF error instead of the
proper authentication error (ErrAuthorization, ErrAuthExpired, etc.),
making it difficult for users to diagnose connection failures.

The fix defers the close frame's io.EOF when there is already pending
data, storing it in a new closeErr field. The pending data is returned
first, and the deferred error is returned on the subsequent Read() call.

Signed-off-by: Waldemar Quevedo <wally@nats.io>

Coverage Stats

14568 of 17055 relevant lines covered (85.42%)

32472.97 hits per line

nats-io / nats.go / 23545171746 / 1
86%
main: 86%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 23545171746.1

nats-io / nats.go / 23545171746 / 1 86% main: 86%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 23545171746.1

nats-io / nats.go / 23545171746 / 1
86%
main: 86%

README BADGES
x