On 23 November 2017 at 20:18, Christophe Demarey <christophe.demarey@inria.fr> wrote:

> Le 23 nov. 2017 �� 12:34, Norbert Hartl <norbert@hartl.name> a ��crit :
>
>
>
>> Am 23.11.2017 um 11:39 schrieb Christophe Demarey <christophe.demarey@inria.fr>:
>>
>> Hi Norbert,
>>
>> I understand your point of view that others probably share.
>> I also agree the situation is very bad: Inria took too much time to investigate the problem and now, renater also ���
>> The question is: would it be really better outside Inria? Maybe ... maybe not ���
>
> Maybe that is the point. It is not a question if it works better outside because it will. The problem we have is so serious that it will be hard to find elsewhere. I can only repeat: It is not the download that fails which TCP wise means that exactly the thing is downloaded that inria offered. So something below the web server is broken and most probably they have a corrupt storage solution meaning only if you give it broken to the web server the broken thing can be transported in a sane manner.

I���m not confident with the diagnostic.
I never encountered this problem


The problem seems geo-specific.�� So you may never personally observe the problem.�� Of course that can make it near-impossible for����yourself��to troubleshoot.
So consider the engineering principal...�� "If you can't solve the problem, change the problem."�� ��


cheers -ben