So here is what I came up with:
private var bufferedBody: ByteBuffer?
private var bufferedEnd: HTTPHeaders?
And modified guard:
guard case .head(var head) = self.unwrapInboundIn(data) else {
let unwrapped = self.unwrapInboundIn(data)
switch unwrapped {
case .body(let buffer):
switch state {
case .connected:
context.fireChannelRead(self.wrapInboundOut(.body(.byteBuffer(buffer))))
case .pendingConnection(_):
print("Buffering body")
self.bufferedBody = buffer
default:
// shouldnt happen
break
}
case .end(let headers):
switch state {
case .connected:
context.fireChannelRead(self.wrapInboundOut(.end(headers)))
case .pendingConnection(_):
print("Buffering end")
self.bufferedEnd = headers
default:
// shouldnt happen
break
}
case .head(_):
assertionFailure("Not possible")
break
}
return
}
And when glue method is done:
context.fireChannelRead(self.wrapInboundOut(.head(head)))
if let bufferedBody = self.bufferedBody {
context.fireChannelRead(self.wrapInboundOut(.body(.byteBuffer(bufferedBody))))
self.bufferedBody = nil
}
if let bufferedEnd = self.bufferedEnd {
context.fireChannelRead(self.wrapInboundOut(.end(bufferedEnd)))
self.bufferedEnd = nil
}
But even with these modifications it appears to be stuck still.
I suspect my "smart" completion handler for the glue method does not work. The original Connect proxy uses the removeHandler method to do the fireChannelRead but when I try to use it similarly, I get another fatal error:
Fatal error: tried to decode as type IOData but found HTTPPart<HTTPResponseHead, ByteBuffer>
Had no idea option like this exists. My use case is quite performance sensitive but I expect most traffic to be HTTPS and thus go through the SwiftNIO route.
It appears to work with these modifications.