I have a server that responds with binary data and an octet-stream header:

Tere Bina Aadhe Bhi Kya, Tere Bina Adhure KyaTu Hi Btaa O Meri Jaan Tere Bina Bina Hai Purre Kya., Tere Bina Jana Kahaan, O Meri Jaan. O meri jaan ab nahi rehna.

The response is a Buffer, so nock converts it to hex before storing in a file. I've truncated the response here and above, but it should be enough to get the idea.

When reading back from the file, I expect it to be converted back into a Buffer via Buffer.from(response.body, 'hex'). Instead it gets converted into a normal Buffer, e.g. the first byte is 'f', the second byte is '0', instead of one byte 0xf0.

I can work around this for the time being by setting Content-Encoding: identity, which triggers the right nock logic. But it would seem preferable to e.g. read the application/octet-stream response header and try to convert from hex based on that.

Alien Shooter is an action shooter game with epic story and swarms of alien enemies. Download Alien Shooter free games now! If you like this free game, try Alien Shooter 2. Alien Shooter is a top-down shooter Video game that was developed and published by Sigma Team Studios. It was released in September 14, 2003 and platforms in which this installment was published were PC and other parts. Alien shooter download for pc.

Hey @kevinburke can you check if #1067 fixes your problem?

Apologies but I've since moved on from that engagement and probably won't have time to test :( best of luck!

A way to test would probably be to start with the JSON I put up above, read it back into memory, and verify the length of the buffer in memory matches the Content-Length header.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if it’s related. Thank you!