zeekayandHanzo Dev 2c76945f3c fix(test): terminate the websocket handshake headers with CRLF CRLF ...

TestWebSocketUpgradeCase failed deterministically, taking 120s to do it:

    proxy_websocket_test.go:50: Received unexpected error: bad status
    FAIL github.com/hanzoai/ingress/pkg/proxy/fast  120.9s

The stub server wrote its 101 response ending `\r\n\n` — one CRLF and a bare
LF — so the header block was never terminated. HTTP requires CRLF CRLF, and a
parser that waits for it does exactly what was observed: no valid status, then
a wait until the deadline. Both symptoms are the same missing two bytes.

The 120s was the whole cost: five packages in this job were excluded for hanging
and this one sat on top of them.

    before:  FAIL  120.9s
    after:   ok      0.9s

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-01 23:29:19 -07:00

..

builder.go

feat: reset module path to hanzoai/ingress v1 (was v3)

2026-04-12 13:00:48 -07:00

connpool_test.go

Detect and drop broken conns in the fastproxy pool

2024-10-25 14:26:04 +02:00

connpool.go

Chunked responses does not have a Content-Length header

2025-02-14 17:44:04 +01:00

dialer.go

Introduce a fast proxy mode to improve HTTP/1.1 performances with backends

2024-09-26 11:00:05 +02:00

proxy_test.go

feat: reset module path to hanzoai/ingress v1 (was v3)

2026-04-12 13:00:48 -07:00

proxy_websocket_test.go

fix(test): terminate the websocket handshake headers with CRLF CRLF

2026-08-01 23:29:19 -07:00

proxy.go

feat: reset module path to hanzoai/ingress v1 (was v3)

2026-04-12 13:00:48 -07:00

upgrade.go

feat: reset module path to hanzoai/ingress v1 (was v3)

2026-04-12 13:00:48 -07:00