This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] TLS tests with login.live.com
- Previous message (by thread): [atlas] TLS tests with login.live.com
- Next message (by thread): [atlas] Three improvement suggestions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Mon May 29 14:04:40 CEST 2017
On 2017/05/29 14:02 , Stephane Bortzmeyer wrote: >> My guess is that the measurement code sends something the other side >> doesn't like and then the server responds with something the Atlas >> code doesn't understand. > > Any way to debug it in more detail? I guess the first step would be look at the interaction in wireshark to see what the server is sending back. Note that at the moment, the probes do not include any SNI information. But a quick test suggests that that is not the cause of the problem. Philip
- Previous message (by thread): [atlas] TLS tests with login.live.com
- Next message (by thread): [atlas] Three improvement suggestions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]