Dear Borja,
Thank you for your offer, but I already found out what I wanted for
fixed source IP address and several seconds delays (that firewalls are
ok with it). For "real" research much more would need to be done, but I
don't have enough time and resources for it now.
Just in case someone
TLS tests from the Atlas probes work for me, for every server... *but*
login.live.com, for which I always get timeouts (it works with other
TLS clients).
Measurement #8775150 if someone has an idea...
On Mon, May 29, 2017 at 01:41:45PM +0200,
Stephane Bortzmeyer wrote
a message of 5 lines which said:
> TLS tests from the Atlas probes work for me, for every server... *but*
> login.live.com, for which I always get timeouts (it works with other
> TLS clients).
Could it be related to this erro
On 2017/05/29 13:53 , Stephane Bortzmeyer wrote:
> On Mon, May 29, 2017 at 01:41:45PM +0200,
> Stephane Bortzmeyer wrote
> a message of 5 lines which said:
>
>> TLS tests from the Atlas probes work for me, for every server... *but*
>> login.live.com, for which I always get timeouts (it works w
On Mon, May 29, 2017 at 01:58:13PM +0200,
Philip Homburg wrote
a message of 24 lines which said:
> No, the Atlas code is nowhere near advanced enough to do that.
OK, but the coincidence is funny :-)
> My guess is that the measurement code sends something the other side
> doesn't like and the
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 a
