The problem is that deflate encoding in http is a giant mess, because Microsoft originally implemented it incorrectly in IE, and so then lots of servers started returning incorrectly-encoded deflate data so that IE could read it, but then other servers implemented it correctly, and now both versions are widely used, and so any client-side implementation has to pick one of the two versions, and try to decode the data according to that, and then if that fails, retry using the other version.

Plus, given that deflate provides absolutely advantage over gzip anyway, and all clients implement gzip, there is no reason for servers to use deflate, other than sadism.

Anyway, if you submitted a working patch, I'd take it, but I have no plans to write it myself.

Oh i wasn't aware of this behaviour. I just noticed that deflate is missing when toying around with a self-written server. 

That explains the difficulty of implementing it. I thought you could just use libz for that and it'll work out fine.

ok, if you don't actually need deflate i'm going to close this