Peter

I added first workaround to only store HTTP/OK responses for now: https://github.com/equalitie/ouinet/commit/cb31fe4cc4d8cf4cabe18afdba00c5512fd23eb3

Disabled GNUnet and it still seems to appear. Possibly related to [IPFS memory issues](https://github.com/ipfs/go-ipfs/issues/2645).

I've done a little work in this regard [here](https://github.com/equalitie/ouinet/commit/388ee16d0c044a29d85c007324e7eea4900dc80a), but I did not think the `Transfer-Encoding` part as thoroughly as you did, so I may have introduced some new bugs...

@lkalneus, correct me if I'm wrong, but it seems you're trying to build Boost-for-Android on windows. The script is [known to not work on windows](https://github.com/MysticTreeGames/Boost-for-Android/issues/27). The fastest solution for you...

I was dealing with support for zlib in [equalitie/Boost-for-Android fork of this project](https://github.com/equalitie/Boost-for-Android), in [this 67ed5c6e86 commit](https://github.com/equalitie/Boost-for-Android/commit/67ed5c6e8669073fd5cb939e5914662057514d00) in particular. Unfortunately I had been lazy to push it to the upstream....

> If you like we could discuss the changes and of course a small guide on how to maintain it in the future Yes, I'm up for it. The above...

I think you've accidentally copy pasted the path to the NDK wrong. It shouldn't start with the dollar sign ($E:/mayur_...).

@jeevan-ghule , I removed the patch for bootstrap.log (not sure how it got there) in this branch: https://github.com/inetic/Boost-for-Android if you give it a go, try the following commands: $./build-android.sh --clean...

The path to the ndk indeed looks incorrect. It should point to the directory which contains the RELEASE.TXT file.

@jeevan-ghule , the command Moritz had in mind was actually: $ cat E:/mayur_eclipse/Android-sdk/android-ndk-r8e/RELEASE.TXT (without the colon after the _cat_ command :) )