Difficulty debugging https POST to microsoft Azure.

RE: Difficulty debugging https POST to microsoft Azure.

JVantol — Mon, 20 Apr 2020 14:11:11 GMT

Didrik,

I took a modem trace, and was able to get it decoded by one of your colleagues. I'm pretty much a HTTPS/TLS newbie, so I'll have to spend some time getting up to speed on what it's supposed to look like. If you've got any suggested reference materials for learning the ins and outs of TLS I'm all ears.

Thanks,

Josh

RE: Difficulty debugging https POST to microsoft Azure.

Didrik Rokhaug — Mon, 20 Apr 2020 13:47:04 GMT

[quote user="JVantol"]Is there a plan and a timeline to support SNI? Clearly there's awareness of the need, as the interface (socket_hostname_set) is there.[/quote]

Sadly, I can not comment on that. Questions about future releases should be directed to your Regional Sales Manager.

[quote user="JVantol"]Also per my other ticket # 248033 is there a way to hook wireshark to the modem trace and discern for myself what's going on?[/quote]

As my colleague answered in that ticket, your proposal has been forwarded to our product management team. Other than that, I am again unable to provide further comments.

[quote user="JVantol"]Is there a way to know for sure that the lack of SNI is causing this failure?[/quote]

A modem trace would be the best way to say for sure 🙂

RE: Difficulty debugging https POST to microsoft Azure.

JVantol — Fri, 17 Apr 2020 14:01:22 GMT

We cannot disable SNI, as we don't control the other end. Is there a reason why the connect does not fail, nor does the send? Clearly it isn't working, but no failure is coming back. Is there a way to know for sure that the lack of SNI is causing this failure?

Is there a plan and a timeline to support SNI? Clearly there's awareness of the need, as the interface (socket_hostname_set) is there.

Also per my other ticket # 248033 is there a way to hook wireshark to the modem trace and discern for myself what's going on?

RE: Difficulty debugging https POST to microsoft Azure.

Didrik Rokhaug — Fri, 17 Apr 2020 13:37:02 GMT

Hi.

We do not support Server Name Indication (SNI) at this point, which is probably the reason why you connect fails.

One (bad) way to work around that is to disable hostname verification. However, that has some obvious security problems.

Best regards,

Didrik