Boris Smidt

@sulis can you merge?

I also updated the netty version in this PR but added the new client codec options to the httpClientCodec client. in : #1804

it seems it hasn't been accepted yet. nor is my branch 'accepted'. I guess we have to be patient.

how would that work then on the go side? would you get a special websocket implementation that then gives back somekind of 'virtual' websocket?

Would it be technically feasible? (i was trying implement it but i have never written go before :smile: )

I will try to implement it in scala, i'm more experienced with that, and if it was easy to implement i will port it to go and the typescript client.

I tried to implement it in go but i get an ```INFO[0000] streamId:1 header:{headers:{key:"Content-Type" value:"text/plain; charset=utf-8"} headers:{key:"X-Content-Type-Options" value:"nosniff"} status:500} ``` so i can get the headers back to the client...

@hexfusion Thank you that really helped, after adding the framing like typescript, i was able to make the requests work (streaming and unary calls). Currently i have added the 'websocket...

I will continue to work today on it, i can open a pr and you can give me some advice? On the go part? On Sat, Feb 19, 2022, 16:20...

I'm planning to go to a separate package to only support the 'grpc-websocket' protocol (instead of grpc-web) to make the scope of the package more clear and significantly reduce the...