Requests that include an accept gzip header break

[hnnesv]

If a request includes the header Accept-Encoding: gzip the following error occurs:

info: Routing http(s) request
zlib.js:222
    callback(null, buf);
    ^
TypeError: undefined is not a function
    at Gunzip.onEnd (zlib.js:222:5)
    at Gunzip.EventEmitter.emit (events.js:129:20)
    at _stream_readable.js:898:16
    at process._tickDomainCallback (node.js:372:11)

[BMartinos]

@rcrichton @devcritter I don't think the gzip issue hasn't been resolved in a module update. When testing on my local instance i was able to send a basic curl command, adding (-H "Accept-Encoding: gzip,deflate") which went through fine. The transaction gets created and i can see the Accept-Encoding: gzip in the transaction header.

However when i tested this on the preprod server the transactions is stuck in processing. I used the curl command with the certificate details which works fine without the Accept-Encoding header, but when i add it in it stays in processing. (Prob due to the error described above).
curl -v --insecure --key test/_/key.pem --cert test/_/cert.pem https://openhim-preprod.jembi.org:5000/sample/api -H "JsonStub-User-Key: *******************" -H "JsonStub-Project-Key: *************" -H "Accept-Encoding: gzip,deflate"

I am not sure if this is a issue only on pre-prod or a certificates issue?

[rcrichton]

Maybe the module on preproduction need to be updated?

[rcrichton]

@BMartinos what do you think we should do here? Was their anything useful in the server logs that point to an exception occurring? Is it the same exception that Hannes noticed?

[hnnesv]

To recreate the issue, try setting up a channel that routes to a server that supports gzip responses, e.g. try setting up a passthrough to something like apache. The issue occurred when I was routing requests to such a service and they were responding with compressed data.

[rcrichton]

Closed in #261