Rust warp::hyper::client and hyper_tls leads to "decoding error" on MacOS only

Question

DragisBlade OP

Created Feb ’23

Replies 3

Boosts 0

Participants 3

I am new to this Forum and Community and hope, thats correct what I will do here.

I currently tracking down a very strange issue with HTTPS-Client requests on MACOS.

I am using Rust with the libraries Warp and Hyper-Client, including Hyper-TLS to create a Webserver and another Backend-Application calling that Webservers interface. Actually, everything works well, on windows, and linux, even on macos.

But as soon as I execute a HTTPS-Call from within my application running on MacOS to any other Operating System it failes with the error error trying to connect: decoding error

The Error looks quite similar to this one here

Noticeable Things so far:

If I use localhost to connect to my application running on the same Mac it works well!
If I use <local-ip> instead, I get the error.
No matter what I do, adding Root Cert to the HTTPSHandler, to MACOS or disableing all cert checks (danger_accept_invalid_hostnames(true).danger.accept_invalid_certs(true)) the error remains.
Calls from Safari and Chrome on the same MacOS as well as other devices to my Application working well and are secured (Certificates are valid (even in MacOS))
A Call with the same client configuration to some public web page, like https://google.de%C2%A0works well. Also local Webservers with HTTP (without S) can be called without any problem.

I already created a Issue on Github but hence this behaviour is also dedicated to MacOS, there has to be a difference between macos and other operating systems counting into this. So I now try also here too...

I would be very grateful for any thought or idea how to proceed ... in hope that I did not discover a hidden bug somewhere inside some library... thanks in advance!

Boost

Answer 1

MobileTen OP

Feb ’23

Not an Apple product. The maintainers of that project will have to resolve the issue in their time.

0

Answer 2

DTS Engineer OP

Apple

Feb ’23

It’s hard for Apple folks to give you an answer here because we have no idea how this feature is implemented. It’s possible that it’s Rust code all the way down but it’s also possible that the Rust code is cutting over to an Apple API at some point. Someone familiar with the Rust code need to dig into it to see whether the symptoms you’re seeing are the result of an Apple API misbehaving or an issue that’s entirely internal to the Rust code.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 3

DragisBlade OP

Feb ’23

Well, yes, I really can understand that. I will try get in touch with those library developers.

But I want to say thank you for the very quick response, sO:

Thanks!

0