WebSocket through malai fails

[RagibHasin]

Websocket upgrade fails with 400 Bad Request with a message

Connection header did not include 'upgrade'

Investigation using Wireshark shows that indeed the forwarded request does not contain the Upgrade: websocket header.

[RagibHasin]

I think this is being caused by

kulfi/kulfi-utils/src/http.rs

Lines 11 to 17 in 11d4d3f

	for (k, v) in r.headers {
	let k = match k {
	Some(v) => v.to_string(),
	None => continue,
	};
	headers.push((k, v.as_bytes().to_vec()));
	}

dropping repeated headers.

Using by-refenece iteration might solve the problem but I can't figure out how to test http-bridge functionality locally.

[siddhantk232]

I'd do the following to test the bridge functionality locally:

# Get an id52 that exposes a local websocket server running on port 3000
malai http 3000 --public
# (in another terminal)
malai http-bridge -t <id52 of the ws server running on 3000>

The http-bridge with the -t flag will print a localhost url. Visiting it in your browser will forward your request from the bridge to your exposed service.

[RagibHasin]

Okay, now Websocket request and response 101 Switching Protocol pass through but other errors crop up.

On the Websocket server side it is IO error: An established connection was aborted by the software in your host machine. (os error 10053). I'm on Windows (11 23H2) btw.

On host side it is:

2025-07-31T09:56:15.410180Z ERROR malai::expose_http: failed to accept bidirectional stream: closed by peer: 0

Location:
    <snipped>\kulfi\kulfi-utils\src\utils.rs:102:32
2025-07-31T09:56:15.411083Z ERROR malai::expose_http: connection error3: closed by peer: 0

Location:
    <snipped>\kulfi\kulfi-utils\src\utils.rs:102:32

On bridge side it is:

2025-07-31T09:55:15.336834Z ERROR malai::http_bridge: connection error2: hyper::Error(IncompleteMessage)

[siddhantk232]

I asked @amitu about this in our discord server:

Our http proxy is written in a request response mode. We read the entire request. Then we send the entire request to peer. Peer makes the corresponding http request and send to http server where peer waits for entire response and send it back to original peer which then returns the entire http reinsert to original client. This is not what websocket expects where once http connection is established it goes in a two way streaming mode. In the http proxy code (http proxy over iroh vs http over iroh) we have implemented two way proxying after initial http handshake which is what we have to do for our regular http also now. Our http over iroh code should do the same. We have to be websocket aware. And possibly http long poll aware.

Feel free to ping amitu here or join our discord if you need help solving this.