Re: TR: COSOLUCE : Urgent --> Problème de validation de schéma

Thank you for your mail.  (I regret that I am unable to respond in =
French; my
apologies.)

I wonder if the problem may be related to the measures W3C has =
undertaken to=20
deal with the problem of excessive DTD and schema traffic [1, 2].  DTD =
and XSD=20
resources change very slowly and can therefore be cached very =
effectively, and
W3C serves such resources with appropriate cache-control headers.  But =
some
programs and libraries (including apparently some in very wide use) =
insist on=20
hitting the W3C servers every time they wish to use a DTD or schema; the =
result=20
has been a very high load on W3C's network connections and servers.  In =
order to
deal with the problem, W3C's system administrators have set things up so =
that=20
DTDs and schema documents are served very slowly; impatient software may=20=

misinterpret this as a network timeout, and perhaps that is what is =
happening in=20
this case.  But IP addresses which hit the W3C site repeatedly for the =
same resource
within a very short period of time may also be blacklisted, especially =
if the user agent
string is not set in such a way as to allow the software responsible for =
the requests to
be identified reliably.  That might also explain the behavior observed.=20=


There are several measures you, or any software developer or user =
affected by
these issues can undertake.

- You can and should set up and use some mechanism to allow the schema =
documents
in question to be retrieved without hitting the W3C server.  A local =
caching proxy
is one possibility; the use of an XML Catalog is another.  Pointers to =
further information=20
on these is available in the blog post at [2].

- As software developers, you should ensure that your software can use =
XML Catalogs
for stable resources like the DSig schema, and that it is easy for the =
user to tell the
software where to find the catalog.  (My personal view is that it's =
helpful if you ship a
catalog with your software and make use of a catalog the default, but =
some smart
people disagree with me on that.)

- As software developers, you should also ensure that when you request a=20=

schema from W3C, you use the appropriate facilities of your http library =
to set
an informative user-agent string, so that cases of malconfigured =
installations of your
software can be identified and fixed.

There may be other steps you can take; I refer you to [2] for other =
ideas.

It is possible, of course, that I have completely misunderstood the =
nature of the
issue and that the origin of your trouble is completely unrelated to =
W3C's=20
defensive measures against excessive DTD and schema traffic.  (But even =
if
the problem is some other network issue, a local cache or an XML catalog =
will
help to defend against it.)

I hope this helps.

--C. M. Sperberg-McQueen
  Black Mesa Technologies LLC

[1] http://www.w3.org/Help/Webmaster.html#slowdtd
[2] =
http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic/




On Mar 1, 2013, at 6:08 AM, <[email protected]> =
<[email protected]> wrote:

> Merci pour votre retour
> =20
> Voici la r=E9ponse de notre =E9quipe r=E9seau =E0 ce sujet.
> =20
> Par la m=EAme occasion, pouvez-vous de votre c=F4t=E9 tester la =
validation du sch=E9ma de ce fichier exemple (en pj) ?
> =20
> Encore merci
> =20
> Cordialement,
> =20
> <image002.gif>
>        Julien DURAND   I   Service D=E9veloppement
>          Technopole H=E9lioparc - 2 av. Pierre Angot - 64053 Pau Cedex =
9
>          Tel : 05.59.14.03.40 - Fax : 05.59.02.03.18
> =20
> De : Pascal Clemot=20
> Envoy=E9 : vendredi 1 mars 2013 14:04
> =C0 : COSOLUCE - Julien DURAND
> Objet : RE: COSOLUCE : Urgent --> Probl=E8me de validation de sch=E9ma
> =20
> pas un pb de standard, mais bien un pb r=E9seau.
> =20
> la requ=EAte http semble =EAtre interrompue par un =E9quipement r=E9seau=
 interm=E9diaire au bout de 15 secondes
> cela ressemble =E0 un timeout TCP=85
> =20
> <image001.png>
> =20
> De : COSOLUCE - Julien DURAND=20
> Envoy=E9 : vendredi 1 mars 2013 13:52
> =C0 : Pascal Clemot
> Objet : TR: COSOLUCE : Urgent --> Probl=E8me de validation de sch=E9ma
> =20
> Pascal,
> =20
> Pourrais-tu m=92aider =E0 r=E9pondre =E0 cette demande stp ?
> =20
> Thanks
> =20
> <image002.gif>
>        Julien DURAND   I   Service D=E9veloppement
>          Technopole H=E9lioparc - 2 av. Pierre Angot - 64053 Pau Cedex =
9
>          Tel : 05.59.14.03.40 - Fax : 05.59.02.03.18
> =20
> De : Bernard Odier [mailto:[email protected]]=20
> Envoy=E9 : vendredi 1 mars 2013 12:14
> =C0 : COSOLUCE - Julien DURAND; [email protected]
> Cc : [email protected]; _Cosoluce Cyan
> Objet : RE: COSOLUCE : Urgent --> Probl=E8me de validation de sch=E9ma
> =20
> Bien re=E7u, cependant le bureau France du W3C est un bureau de =
repr=E9sentation, sans ressource d'experts ni de diagnostic.
> =20
> Le W3C ne fait qu'=E9mettre des sp=E9cifications, mais n'est pas =
organis=E9 pour faire le suivi de leur mise en oeuvre, et ne fait aucun =
"blocage administratif" .
> =20
> Par ailleurs, s'il s'agit d'un probl=E8me de connexion TCP (?) , alors =
c'est un probl=E8me de r=E9seau, et non de standard du web.
> =20
> Afin de me permettre d'identifier un expert au W3C quelque part dans =
le monde pour aller plus loin =E9ventuellement, il faudrait me dire quel =
est =E0 votre avis le standard du web qui poserait probl=E8me :  http , =
autre ?
> =20
> D=E9sol=E9 de ne pas pouvoir intervenir davantage =E0 ce stade.
> =20
> Cdlt,
> =20
> Bernard ODIER
> Office Manager, W3C France Office
> C=B0 Inria, 23 Avenue d'Italie, Paris 75013 France
> [email protected]
> +33 6 07 71 81 16
> www.w3.org
>=20
> =20
> =20
> =20
> =20
> =20
> =20
> De : [email protected] [mailto:[email protected]]=20
> Envoy=E9 : vendredi 1 mars 2013 11:33
> =C0 : [email protected]
> Cc : [email protected]; [email protected]
> Objet : COSOLUCE : Urgent --> Probl=E8me de validation de sch=E9ma
>=20
> Bonjour,
> =20
> Nous sommes =E9diteur de logiciel et notamment du logiciel Cyan qui =
g=E8re l=92=E9tat civil des collectivit=E9s.
> =20
> Je me permets de solliciter votre aide car depuis quelques jours nous =
avons un souci de validation de sch=E9ma que nous n=92avions pas =
auparavant.
> =20
> Un fichier exemple est en pi=E8ce jointe.
> =20
> Le validateur de notre logiciel retourne cette erreur et bloque donc =
la transmission du fichier =E0 l=92INSEE qui nous a confirm=E9 ne pas =
avoir fait de modifications sur leurs sch=E9mas :
> <image003.jpg>
> =20
> Nous =E9quipons environ 300 communes qui =E0 l=92heure actuelle ne =
peuvent plus transmettre ces bulletins =E0 l=92INSEE..
> =20
> Pouvez-vous nous venir en aide suite =E0 ce blocage ?
> =20
> Pour info, nous avons effectu=E9 une multitude de tests de notre c=F4t=E9=
 (antivirus, pare-feu, analyse des paquets r=E9seaux, v=E9rification =
avec l=92INSEE, etc.)
> Une des pistes peut =EAtre l=92analyse des trames ci-dessous :
> =20
> Connexion au sch=E9ma =
http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xs=
d :
> =20
> -           la connexion est coup=E9e au bout de 15 secondes pour le =
motif =AB Request forbidden by administrative rules =BB :
> =20
> <image004.jpg>
> =20
> Explications de la capture :
> 1.       Ligne 885 =E0 Connexion demand=E9e au sch=E9ma =
http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xs=
d
> 2.       Ligne 1724 =E0 (15sec. plus tard) : on arrive =E0 d=E9chiffrer =
(dans le d=E9tail) le message d=92interdiction.
> =20
> =20
> En vous remerciant d=92avance,
> =20
> =20
> Cordialement,
> =20
> <image002.gif>
>        Julien DURAND   I   Service D=E9veloppement
>          Technopole H=E9lioparc - 2 av. Pierre Angot - 64053 Pau Cedex =
9
>          Tel : 05.59.14.03.40 - Fax : 05.59.02.03.18
> =20
> <Bulletin_Test.xml>

--=20
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com=20
* http://cmsmcq.com/mib                =20
* http://balisage.net
****************************************************************