Not picking up linux binary for System.Net.Http.dll

[Tratcher]

aspnet/Security#415

Dnx embeds the coreclr binaries for linux/mac, including System.Net.Http. Security also uses System.Net.Http, but the package only contains the windows binaries. @davidfowl said that dnx should load the linux binary for you, but that the directory structure is wrong so it doesn't work right now. Fix it.

Eventually the coreclr packages will contain both windows and linux binaries.

@BrennanConroy

[muratg]

Where would this assembly be loaded from instead? Is it special casing for Linux? And for OS X too?

[muratg]

⌚

[analogrelay]

Since at the moment we embed System.Net.Http in the DNX, we'd place it in the DNX runtime folder.

[BrennanConroy]

This could probably be fixed if we copy the dll to the bin folder as well as keep it in the Tooling folder

[muratg]

Yes, I think we should do that.

[zhangxin511]

Hey gentles,
With helps from @Tratcher and our architecture, I am able to get some response using HttpClient in Linux:
We upgraded dnvm to coreclr beta8-15618, and copied System.Net.Http.dll and System.Net.Http.Native.so from ~/.dnx/runtimes/dnx-coreclr-linux-x64.1.0.0-beta8-15618/bin/lib/Microsoft.Dnx.Tooling/ to ~/.dnx/runtimes/dnx-coreclr-linux-x64.1.0.0-beta8-15618/bin/, and use HttpClient methods to get content from web servers. However, I am not able to read the Content of response Linux, while the header information seems fine. The same code works fine in windows.

Is there anything I am missing?

Thank you!

[Tratcher]

Is the response compressed? I wonder if the Linux client isn't auto-decompressing.

[zhangxin511]

Yes, the response is compressed. The header returns when GetAsync to google.com:
Content-Type: text/html; charset=ISO-8859-1
Content-Encoding: gzip
Content-Length: 50309

But even I tried removing the compression or decompress after getting the content I still not getting anything. You can find the source code at https://www.dropbox.com/sh/iukr2l4elcqp77k/AACXrYXo2rrcc4PCn9taJGhaa?dl=0

Thank you for your continue helps!

[Tratcher]

@BrennanConroy have you seen any issues like this? Are there any similar corefx bugs outstanding?

[BrennanConroy]

I haven't tried anything like this, the client may have more features now, especially since we haven't tried a new one in a couple weeks. We should try this when we grab the new bits.

[BrennanConroy]

Fixed with the latest CoreCLR bits, waiting for a build to go through on our side.

[BrennanConroy]

Fixed by a few different changes, wont list them all here, but one is a64c8d5