webassembletool-users — ESIGate user list

Re: [EsiGate-users] esigate et HTTPS

[Francois-Xavier B. <fra...@ce...>]

Bonsoir,

Si Spring web flow prend la valeur de request.getScheme(), on doit pouvoir
ajouter un servlet filter qui surcharge cette méthode pour passer la valeur
provenant du header X-forwarded-proto de EsiGate.


Le 12 juillet 2013 15:44, Nicolas Richeton <nic...@gm...> a
écrit :

> Bonjour Alban,
>
> Je vois 2 solutions:
> - soit appeler l'application métier en https (remoteUrl=https://....)
> - soit ajouter une extension qui intercepte les 302 pour cette application
> et qui réécrit le scheme. [1]
>
> Sinon, il devrait y avoir une entête X-Forwarded-Proto dans les requêtes
> qui partent vers l'application métier, mais Spring webflow n'a pas l'air de
> se baser dessus.
>
> Nicolas
>
> [1] http://www.esigate.org/reference.html#Extending_and_customizing
>
> Le 12 juil. 2013 à 14:57, Alb...@av... a écrit :
>
> Bonjour
>
> j'avais une question relative à esigate et son utilisation dans notre
> environnement.
>
> Actuellement nous avons un reverse proxy esigate en frontal d'un serveur
> jahia 6 (context /jahia) et d'un serveur d'application métier (context
> /servlet).
> Dans l'application métier nous utilisons le framework Spring Webflow qui
> fait un *POST - REDIRECT - GET* lors d'un POST de formulaire.
>
> Lorsque nous sommes en *HTTP*, il n'y a absolument aucun problème, le
> framework se comporte comme souhaité : *POST (http) - REDIRECT - GET
> (http)*.
> En revanche lorsque nous postons en *HTTPS*, il fait un *POST(https) -
> REDIRECT (location = **http://....* <http://.../>*.) - GET (http)*.
> Cela n'est pas dû au framework car en réalité comme il passe par esigate,
> qui lui transmet un POST en http, il considère le request.getScheme() comme
> http.
> Si j'appelle la même page sans passer par esigate, je retrouve un
> comportement attendu *POST (https) - REDIRECT(location = **https://....*<https://.../>
> *.) - GET (https).*
>
> Le framework que nous utilisons se base sur request.getHost() et
> request.getScheme() pour obtenir les informations nécessaires à l'écriture
> du response header *Location* du *REDIRECT (302)*
> Afin de conserver le bon host, dans le fichier properties de esigate nous
> avons ajouté *preserveHost=true*.
>
> Cependant, existe-t-il quelque chose de similaire pour conserver les
> scheme (http / https) ?
> Ou bien une astuce pour remédier à ce problème nous conviendrait
> parfaitement.
>
> D'avance merci.
> Cordialement
>
>
> Alban DELATTRE
> Eurofil / Aviva - Service Informatique
> 17 rue Pierre Gilles de Gennes
> 76 130 Mont Saint Aignan
> 02.76.01.53.81
>
>
> Préservons la planète : n’imprimez cet e-mail que si nécessaire.
>  ********************************************
> Les informations contenues dans ce message électronique sont destinées à
> l'usage exclusif du (des) destinataire(s) nommé(s).
> Toute divulgation, distribution ou reproduction, même partielle, en est
> strictement interdite.
> Si vous recevez ce message par erreur, veuillez le notifier à  son
> émetteur par retour, et le détruire ainsi que tous les documents qui y sont
> attachés.
>
> The information contained in this email is intended solely for the use of
> the individual or entity to which it is addressed.
> Partial or total disclosure, distribution or reproduction of its contents
> is strictly prohibited.
> If you have received this communication in error, please notify us
> immediately by responding to this email, and then delete the message and
> its attached files from your system.
>
> *********************************************------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
>
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk_______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>
>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>
>

Re: [EsiGate-users] esigate et HTTPS

[Nicolas R. <nic...@gm...>]

Bonjour Alban, 

Je vois 2 solutions: 
- soit appeler l'application métier en https (remoteUrl=https://....) 
- soit ajouter une extension qui intercepte les 302 pour cette application et qui réécrit le scheme. [1]

Sinon, il devrait y avoir une entête X-Forwarded-Proto dans les requêtes qui partent vers l'application métier, mais Spring webflow n'a pas l'air de se baser dessus. 

Nicolas 

[1] http://www.esigate.org/reference.html#Extending_and_customizing

Le 12 juil. 2013 à 14:57, Alb...@av... a écrit :

> Bonjour 
> 
> j'avais une question relative à esigate et son utilisation dans notre environnement. 
> 
> Actuellement nous avons un reverse proxy esigate en frontal d'un serveur jahia 6 (context /jahia) et d'un serveur d'application métier (context /servlet). 
> Dans l'application métier nous utilisons le framework Spring Webflow qui fait un POST - REDIRECT - GET lors d'un POST de formulaire. 
> 
> Lorsque nous sommes en HTTP, il n'y a absolument aucun problème, le framework se comporte comme souhaité : POST (http) - REDIRECT - GET (http). 
> En revanche lorsque nous postons en HTTPS, il fait un POST(https) - REDIRECT (location = http://.....) - GET (http). 
> Cela n'est pas dû au framework car en réalité comme il passe par esigate, qui lui transmet un POST en http, il considère le request.getScheme() comme http. 
> Si j'appelle la même page sans passer par esigate, je retrouve un comportement attendu POST (https) - REDIRECT(location = https://.....) - GET (https). 
> 
> Le framework que nous utilisons se base sur request.getHost() et request.getScheme() pour obtenir les informations nécessaires à l'écriture du response header Location du REDIRECT (302) 
> Afin de conserver le bon host, dans le fichier properties de esigate nous avons ajouté preserveHost=true. 
> 
> Cependant, existe-t-il quelque chose de similaire pour conserver les scheme (http / https) ? 
> Ou bien une astuce pour remédier à ce problème nous conviendrait parfaitement. 
> 
> D'avance merci. 
> Cordialement 
> 
> 
> Alban DELATTRE
> Eurofil / Aviva - Service Informatique
> 17 rue Pierre Gilles de Gennes
> 76 130 Mont Saint Aignan
> 02.76.01.53.81
> 
> 
> Préservons la planète : n’imprimez cet e-mail que si nécessaire.
> ********************************************
> Les informations contenues dans ce message électronique sont destinées à  l'usage exclusif du (des) destinataire(s) nommé(s). 
> Toute divulgation, distribution ou reproduction, même partielle, en est strictement interdite.
> Si vous recevez ce message par erreur, veuillez le notifier à  son émetteur par retour, et le détruire ainsi que tous les documents qui y sont attachés.
> 
> The information contained in this email is intended solely for the use of the individual or entity to which it is addressed.  
> Partial or total disclosure, distribution or reproduction of its contents is strictly prohibited. 
> If you have received this communication in error, please notify us immediately by responding to this email, and then delete the message and its attached files from your system. 
> *********************************************------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk_______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users

[EsiGate-users] esigate et HTTPS

[<Alb...@av...>]

Bonjour

j'avais une question relative à esigate et son utilisation dans notre 
environnement.

Actuellement nous avons un reverse proxy esigate en frontal d'un serveur 
jahia 6 (context /jahia) et d'un serveur d'application métier (context 
/servlet).
Dans l'application métier nous utilisons le framework Spring Webflow qui 
fait un POST - REDIRECT - GET lors d'un POST de formulaire.

Lorsque nous sommes en HTTP, il n'y a absolument aucun problème, le 
framework se comporte comme souhaité : POST (http) - REDIRECT - GET (http)
.
En revanche lorsque nous postons en HTTPS, il fait un POST(https) - 
REDIRECT (location = http://.....) - GET (http). 
Cela n'est pas dû au framework car en réalité comme il passe par esigate, 
qui lui transmet un POST en http, il considère le request.getScheme() 
comme http.
Si j'appelle la même page sans passer par esigate, je retrouve un 
comportement attendu POST (https) - REDIRECT(location = https://.....) - 
GET (https).

Le framework que nous utilisons se base sur request.getHost() et 
request.getScheme() pour obtenir les informations nécessaires à l'écriture 
du response header Location du REDIRECT (302)
Afin de conserver le bon host, dans le fichier properties de esigate nous 
avons ajouté preserveHost=true.

Cependant, existe-t-il quelque chose de similaire pour conserver les 
scheme (http / https) ? 
Ou bien une astuce pour remédier à ce problème nous conviendrait 
parfaitement.

D'avance merci.
Cordialement


Alban DELATTRE
Eurofil / Aviva - Service Informatique
17 rue Pierre Gilles de Gennes
76 130 Mont Saint Aignan
02.76.01.53.81


Préservons la planète : n’imprimez cet e-mail que si nécessaire.

********************************************
Les informations contenues dans ce message électronique sont destinées à  l'usage exclusif du (des) destinataire(s) nommé(s).
Toute divulgation, distribution ou reproduction, même partielle, en est strictement interdite.
Si vous recevez ce message par erreur, veuillez le notifier à  son émetteur par retour, et le détruire ainsi que tous les documents qui y sont attachés.

The information contained in this email is intended solely for the use of the individual or entity to which it is addressed. 
Partial or total disclosure, distribution or reproduction of its contents is strictly prohibited.
If you have received this communication in error, please notify us immediately by responding to this email, and then delete the message and its attached files from your system.
*********************************************

[EsiGate-users] [Release] Esigate 4.1

[Nicolas R. <nic...@gm...>]

Hi, 

The new Esigate 4.1 release is available from the website and Maven repositories. 

It contains some fixes on 
  - Url rewriting, especially when preserveHost is enabled,
  - Extensions when caching is disabled
  - Cookie management 
  - Http Caching (HttpClient)

It also contains some useful new features : 
  - Page encoding override   (via extension)
  - Mapping configuration in esigate.properties (BETA). Fell free to test this. Old behavior is still available and recommended in the 4.x line. 


Get it from :
http://www.esigate.org


Nicolas.



Detailed changelog : 
https://sourceforge.net/apps/mantisbt/webassembletool/changelog_page.php

Esigate - 4.1
=============

This is mainly a bugfix release. 

Also includes the following fixes from HttpClient : 

HTTPCLIENT 4.2.5
     HTTPCLIENT-1340	 FIXED	Connection re-used in a inconsistent state despite 'Connection: close' after successful authentication	
     HTTPCLIENT-1342	 FIXED	"java.lang.IllegalArgumentException: Host name may not be null" thrown during redirect	
     HTTPCLIENT-1338	 FIXED	Caching of digest credentials broken when server expires nonce (regression bug)	
     HTTPCLIENT-1341	 FIXED	DeflateDecompressingEntity does not call Inflater#end	
     HTTPCLIENT-1299	 FIXED	FileNotFoundException on Cached Variant	
     HTTPCLIENT-1350	 NOT A PROBLEM	Expect/continue does not consistently work	

HTTPCLIENT 4.2.4
     HTTPCLIENT-1311	 FIXED	Interrupt flag is not preserved where InterruptedException is caught	
     HTTPCLIENT-1320	 FIXED	SSLSocketFactory.createSystemSSLContext causes java.security.UnrecoverableKeyException: Password verification failed	
     HTTPCLIENT-1302	 INVALID	AllowAllHostnameVerifier should not access session	
     HTTPCLIENT-1327	 FIXED	BrowserCompatSpec double quotes cookie value when cookie has "expires" attribute	
     HTTPCLIENT-1326	 FIXED	Cannot override DefaultClientConnectionOperator	
     HTTPCLIENT-1312	 FIXED	Decompressing on redirects with redirection support off doesn't work properly	
     HTTPCLIENT-1336	 FIXED	Document Entity-consuming behaviour of HttpClient.execute methods with ResponseHandler param	
     HTTPCLIENT-1305	 FIXED	GGSSchemeBase uses CHUNKED Base64 for Authorization header	
     HTTPCLIENT-1319	 FIXED	InetAddressUtils.isIPv6HexCompressedAddress does not detect excess groups	
     HTTPCLIENT-1315	 FIXED	NTLM or digest authentication using a local user on a domain host doesn't work	
     HTTPCLIENT-1330	 FIXED	missing javadoc jars in maven repository

New alternative for provider mapping : set mappings directly in esigate.properties. This is a 5.0 feature, included for testing in 4.1. Must be enabled manually.

- 0000237: [Core] Backport 0000174: Redirect location with default port specified are incorrectly rewritten when preserveHost=true (nricheton) - resolved.
- 0000230: [Core] Backport of issue 0000229 : NPE on a AsynchronousValidationRequest sent, for the the 'stale while revalidate' mechanism (nricheton) - resolved.
- 0000227: [Core] Backport a beta version of issue 000175 (external configuration) (nricheton) - resolved.
- 0000234: [Core] Update to HTTP client 4.2.5 (nricheton) - resolved.
- 0000232: [Core] Cookie management : ESIGate should replace in user's cookie store new cookies received instead of always adding them (nricheton) - resolved.
- 0000223: [Core] Add HttpResponse to RenderEvent (4.1 backport) (nricheton) - resolved.
- 0000189: [Core] ResourceFixup : StringIndexOutOfBoundsException: String index out of range: -1 (4.1 Backport) (nricheton) - resolved.
- 0000188: [Core] Unit tests does not fire fetch events (4.1 backport) (nricheton) - resolved.
- 0000181: [Core] Urls with parameters only (?param=value) are broken by ResourceFixUpRenderer (nricheton) - resolved.
- 0000179: [General] New home page (nricheton) - resolved.
- 0000190: [Core] Page encoding broken when charset is missing in http headers (4.1 backport) (nricheton) - closed.
- 0000185: [Core] Extensions : Fetch events are not fired when cache is disabled. (nricheton) - closed.

Re: [EsiGate-users] Clustering ESIGate

[Nicolas R. <nic...@gm...>]

Hi, 

The recommended way is to not use sessions if you can : 
 - use discardCookies and forwardCookies directives to ensure no cookies are stored in esigate. With this, esigate will not create sessions at all (stateless)
 - use several instances with any loadbalancer
 - You can share the cache between instances using memcached or a replicated ehcache (cacheStorage directive) for better hit ratio, but this is not required.
 - Session replication can be set in backend servers (your applications) if necessary

If you really need cookie storage in esigate, the session replication can be set up in your servlet container using standard documentation. You can also implement a shared cookieManager.

Please tell us if this solves your issue :-)

Nicolas


http://www.esigate.org/reference.html#Configuration_file
Le 14 juin 2013 à 07:44, 謝福明 <aug...@ch...> a écrit :

> Hi
>  
> How to setup ESIGate cluster with session replication??
>         Have any documentation describes this?
>  
>         Thanks.
>  
>  
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev_______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users

[EsiGate-users] Clustering ESIGate

[謝福明 <aug...@ch...>]

Hi

How to setup ESIGate cluster with session replication??
        Have any documentation describes this?

        Thanks.

Re: [EsiGate-users] credentials

[Nicolas T. <nic...@ne...>]

It's a bit embarrassing
we have just started the project the verion of esigate is a version 2.2 
??? Where is my Desert Eagle ?
I understand why it does not work like in the documentation.
apologies.

Nicolas TOQUET

Le 06/05/2013 12:16, Nicolas Richeton a écrit :
> getAuthenticationHandler is here for compatibility purposes only in 
> esigate 4.0, and will be removed in the future.
>
> Defining an authentication handler adds the handler to the extension 
> list.
>
> Since you are adding directly your authentication handler to the 
> extension list (this is the right way to do it with esigate 4.0) , 
> getAuthenticationHandler is not updated. However, you should see your 
> extension being registered in logs. (add some logging in the init part 
> just to be sure).
>
> Be careful, extension configuration *redefines* the extension list. 
> There are some default extensions which will be removed with your 
> configuration. See default value in documentation.
>
> Nicolas
>
>
>
> Le 6 mai 2013 à 12:08, Francois-Xavier Bonnet 
> <fra...@ce... 
> <mailto:fra...@ce...>> a écrit :
>
>> Since EsiGate 4.0 AuthenticationHandler interface has been removed, 
>> so I guess you are using an older version.
>>
>> If you were using 4.0 version, you could see class 
>> GenericAuthentificationHandler 
>> <http://www.esigate.org/esigate-core/xref/org/esigate/authentication/GenericAuthentificationHandler.html> and 
>> your configuration would be correct.
>>
>> With a 3.x version the configuration would have looked like:
>> /author.authenticationHandler=fr.esigate.authentication.CustomUserAuthenticationHandler/
>>
>> I suggest that you migrate to the latest version (4.0). With the new 
>> extension mechanism, you will be able to do a lot more things (not 
>> only authentication) that what you could do in previous versions.
>>
>> 2013/5/6 <nic...@ne... 
>> <mailto:nic...@ne...>>
>>
>>     Hello,
>>
>>     Just to summarize :
>>
>>      1. create a customAuthenticationHandler which implements
>>         AuthenticationHandler (GenericAuthenticationHandler does'nt
>>         exist anymore)
>>      2. add some code in the preRequest(HttpClientRequest request,
>>         ResourceContext requestContext) method
>>      3. add the extension in the driver.properties file  :
>>         extensions=fr.esigate.authentication.CustomUserAuthenticationHandler
>>
>>     Is there any other actions ?
>>     When i test this one in my ctrlcmd :
>>         Driver driver = DriverFactory.getInstance("author");
>>     System.out.println(driverConfiguration.getAuthenticationHandler());
>>     // -->
>>     net.webassembletool.authentication.RemoteUserAuthenticationHandler
>>
>>     My extension
>>     'fr.esigate.authentication.CustomUserAuthenticationHandler' does
>>     not seem to be considered
>>
>>     Here is my driver.properties configuration file :
>>     /author.remoteUrlBase=http://localhost:8080/MagnoliaAuthor///
>>     //author.uriEncoding=UTF-8//
>>     //author.timeout=5000//
>>     //author.useCache=false//
>>     //author.extensions=fr.esigate.authentication.CustomUserAuthenticationHandler/
>>
>>     Thanks
>>     Nicolas TOQUET
>>
>>
>>     Le 06/05/2013 09:39, Francois-Xavier Bonnet a écrit :
>>>     Ok, so you have to write an extension: the extension should
>>>     detect when you are redirected to the login page, then post the
>>>     login form and once authenticated send again the original request.
>>>     Maybe we could think of a generic extension for form-based
>>>     authentication but currently it does not exist.
>>>
>>>     If you need an example on how to do this, you can have a look at
>>>     the implementation for CAS SSO:
>>>     http://www.esigate.org/esigate-cas/xref/org/esigate/cas/CasAuthenticationHandler.html
>>>
>>>     If you decided to write something reusable on other projects,
>>>     remember that contributions to the project are always welcome.
>>>
>>>
>>>     2013/5/6 <nic...@ne...
>>>     <mailto:nic...@ne...>>
>>>
>>>         Hello,
>>>
>>>         It is a form based authentication. The webapp we have to
>>>         query is Magnolia. There is a public and an author instance.
>>>         On the Author instance we have to enter credentials when we
>>>         call a page.
>>>
>>>         Thanks
>>>         Nicolas TOQUET
>>>
>>>
>>>         Le 05/05/2013 22:25, Francois-Xavier Bonnet a écrit :
>>>>
>>>>         Hi,
>>>>
>>>>         Is it basic authentication or form-based authentication ?
>>>>         Which version of EsiGate are you using ?
>>>>
>>>>         Le 5 mai 2013 18:50, "Nicolas TOQUET"
>>>>         <nic...@ne...
>>>>         <mailto:nic...@ne...>> a écrit :
>>>>
>>>>             Hello
>>>>
>>>>             we try to get the response from a page in an author
>>>>             instance protected
>>>>             by login/password.
>>>>             how can we pass the credential (driver.properties ?)
>>>>             There is no proxy.
>>>>
>>>>             Thanks
>>>>             Nicolas
>>>>
>>>>             ------------------------------------------------------------------------------
>>>>             Get 100% visibility into Java/.NET code with
>>>>             AppDynamics Lite
>>>>             It's a free troubleshooting tool designed for production
>>>>             Get down to code-level detail for bottlenecks, with <2%
>>>>             overhead.
>>>>             Download for free and get started troubleshooting in
>>>>             minutes.
>>>>             http://p.sf.net/sfu/appdyn_d2d_ap2
>>>>             _______________________________________________
>>>>             Webassembletool-users mailing list
>>>>             Web...@li...
>>>>             <mailto:Web...@li...>
>>>>             https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>>>>
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
>> Get 100% visibility into your production application - at no cost.
>> Code-level diagnostics for performance bottlenecks with <2% overhead
>> Download for free and get started troubleshooting in minutes.
>> http://p.sf.net/sfu/appdyn_d2d_ap1_______________________________________________
>> Webassembletool-users mailing list
>> Web...@li...
>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>

Re: [EsiGate-users] credentials

[Nicolas R. <nic...@gm...>]

getAuthenticationHandler is here for compatibility purposes only in esigate 4.0, and will be removed in the future.

Defining an authentication handler adds the handler to the extension list. 

Since you are adding directly your authentication handler to the extension list (this is the right way to do it with esigate 4.0) , getAuthenticationHandler is not updated. However, you should see your extension being registered in logs. (add some logging in the init part just to be sure). 

Be careful, extension configuration *redefines* the extension list. There are some default extensions which will be removed with your configuration. See default value in documentation. 

Nicolas



 
Le 6 mai 2013 à 12:08, Francois-Xavier Bonnet <fra...@ce...> a écrit :

> Since EsiGate 4.0 AuthenticationHandler interface has been removed, so I guess you are using an older version.
> 
> If you were using 4.0 version, you could see class GenericAuthentificationHandler and your configuration would be correct.
> 
> With a 3.x version the configuration would have looked like:
> author.authenticationHandler=fr.esigate.authentication.CustomUserAuthenticationHandler
> 
> I suggest that you migrate to the latest version (4.0). With the new extension mechanism, you will be able to do a lot more things (not only authentication) that what you could do in previous versions.
> 
> 2013/5/6 <nic...@ne...>
> Hello, 
> 
> Just to summarize : 
> create a customAuthenticationHandler which implements AuthenticationHandler (GenericAuthenticationHandler does'nt exist anymore)
> add some code in the preRequest(HttpClientRequest request, ResourceContext requestContext) method
> add the extension in the driver.properties file  : extensions=fr.esigate.authentication.CustomUserAuthenticationHandler
> Is there any other actions ?
> When i test this one in my ctrlcmd : 
>     Driver driver = DriverFactory.getInstance("author");
>     System.out.println(driverConfiguration.getAuthenticationHandler());  // --> net.webassembletool.authentication.RemoteUserAuthenticationHandler
> My extension 'fr.esigate.authentication.CustomUserAuthenticationHandler' does not seem to be considered
> Here is my driver.properties configuration file : 
> author.remoteUrlBase=http://localhost:8080/MagnoliaAuthor/
> author.uriEncoding=UTF-8
> author.timeout=5000
> author.useCache=false
> author.extensions=fr.esigate.authentication.CustomUserAuthenticationHandler
> 
> Thanks
> Nicolas TOQUET
> 
> 
> Le 06/05/2013 09:39, Francois-Xavier Bonnet a écrit :
>> Ok, so you have to write an extension: the extension should detect when you are redirected to the login page, then post the login form and once authenticated send again the original request.
>> Maybe we could think of a generic extension for form-based authentication but currently it does not exist.
>> 
>> If you need an example on how to do this, you can have a look at the implementation for CAS SSO:
>> http://www.esigate.org/esigate-cas/xref/org/esigate/cas/CasAuthenticationHandler.html
>> 
>> If you decided to write something reusable on other projects, remember that contributions to the project are always welcome.
>> 
>> 
>> 2013/5/6 <nic...@ne...>
>> Hello, 
>> 
>> It is a form based authentication. The webapp we have to query is Magnolia. There is a public and an author instance. On the Author instance we have to enter credentials when we call a page.
>> 
>> Thanks
>> Nicolas TOQUET
>> 
>> 
>> Le 05/05/2013 22:25, Francois-Xavier Bonnet a écrit :
>>> Hi,
>>> 
>>> Is it basic authentication or form-based authentication ?
>>> Which version of EsiGate are you using ?
>>> Le 5 mai 2013 18:50, "Nicolas TOQUET" <nic...@ne...> a écrit :
>>> Hello
>>> 
>>> we try to get the response from a page in an author instance protected
>>> by login/password.
>>> how can we pass the credential (driver.properties ?)
>>> There is no proxy.
>>> 
>>> Thanks
>>> Nicolas
>>> 
>>> ------------------------------------------------------------------------------
>>> Get 100% visibility into Java/.NET code with AppDynamics Lite
>>> It's a free troubleshooting tool designed for production
>>> Get down to code-level detail for bottlenecks, with <2% overhead.
>>> Download for free and get started troubleshooting in minutes.
>>> http://p.sf.net/sfu/appdyn_d2d_ap2
>>> _______________________________________________
>>> Webassembletool-users mailing list
>>> Web...@li...
>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>> 
>> 
> 
> 
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1_______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users

Re: [EsiGate-users] credentials

[Francois-Xavier B. <fra...@ce...>]

Since EsiGate 4.0 AuthenticationHandler interface has been removed, so I
guess you are using an older version.

If you were using 4.0 version, you could see class
GenericAuthentificationHandler<http://www.esigate.org/esigate-core/xref/org/esigate/authentication/GenericAuthentificationHandler.html>
and
your configuration would be correct.

With a 3.x version the configuration would have looked like:
*
author.authenticationHandler=fr.esigate.authentication.CustomUserAuthenticationHandler
*

I suggest that you migrate to the latest version (4.0). With the new
extension mechanism, you will be able to do a lot more things (not only
authentication) that what you could do in previous versions.

2013/5/6 <nic...@ne...>

>  Hello,
>
> Just to summarize :
>
>    1. create a customAuthenticationHandler which implements
>    AuthenticationHandler (GenericAuthenticationHandler does'nt exist anymore)
>    2. add some code in the preRequest(HttpClientRequest request,
>    ResourceContext requestContext) method
>    3. add the extension in the driver.properties file  :
>    extensions=fr.esigate.authentication.CustomUserAuthenticationHandler
>
> Is there any other actions ?
> When i test this one in my ctrlcmd :
>     Driver driver = DriverFactory.getInstance("author");
>     System.out.println(driverConfiguration.getAuthenticationHandler());
> // --> net.webassembletool.authentication.RemoteUserAuthenticationHandler
>
> My extension 'fr.esigate.authentication.CustomUserAuthenticationHandler'
> does not seem to be considered
>
> Here is my driver.properties configuration file :
> *author.remoteUrlBase=http://localhost:8080/MagnoliaAuthor/**
> **author.uriEncoding=UTF-8**
> **author.timeout=5000**
> **author.useCache=false**
> **
> author.extensions=fr.esigate.authentication.CustomUserAuthenticationHandler
> *
> Thanks
> Nicolas TOQUET
>
>
> Le 06/05/2013 09:39, Francois-Xavier Bonnet a écrit :
>
> Ok, so you have to write an extension: the extension should detect when
> you are redirected to the login page, then post the login form and once
> authenticated send again the original request.
> Maybe we could think of a generic extension for form-based authentication
> but currently it does not exist.
>
>  If you need an example on how to do this, you can have a look at the
> implementation for CAS SSO:
>
> http://www.esigate.org/esigate-cas/xref/org/esigate/cas/CasAuthenticationHandler.html
>
>  If you decided to write something reusable on other projects, remember
> that contributions to the project are always welcome.
>
>
>  2013/5/6 <nic...@ne...>
>
>>  Hello,
>>
>> It is a form based authentication. The webapp we have to query is
>> Magnolia. There is a public and an author instance. On the Author instance
>> we have to enter credentials when we call a page.
>>
>> Thanks
>> Nicolas TOQUET
>>
>>
>> Le 05/05/2013 22:25, Francois-Xavier Bonnet a écrit :
>>
>> Hi,
>>
>> Is it basic authentication or form-based authentication ?
>> Which version of EsiGate are you using ?
>>  Le 5 mai 2013 18:50, "Nicolas TOQUET" <nic...@ne...> a
>> écrit :
>>
>>> Hello
>>>
>>> we try to get the response from a page in an author instance protected
>>> by login/password.
>>> how can we pass the credential (driver.properties ?)
>>> There is no proxy.
>>>
>>> Thanks
>>> Nicolas
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Get 100% visibility into Java/.NET code with AppDynamics Lite
>>> It's a free troubleshooting tool designed for production
>>> Get down to code-level detail for bottlenecks, with <2% overhead.
>>> Download for free and get started troubleshooting in minutes.
>>> http://p.sf.net/sfu/appdyn_d2d_ap2
>>> _______________________________________________
>>> Webassembletool-users mailing list
>>> Web...@li...
>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>>>
>>
>>
>
>

Re: [EsiGate-users] credentials

[Nicolas T. <nic...@ne...>]

Hello,

Just to summarize :

 1. create a customAuthenticationHandler which implements
    AuthenticationHandler (GenericAuthenticationHandler does'nt exist
    anymore)
 2. add some code in the preRequest(HttpClientRequest request,
    ResourceContext requestContext) method
 3. add the extension in the driver.properties file  :
    extensions=fr.esigate.authentication.CustomUserAuthenticationHandler

Is there any other actions ?
When i test this one in my ctrlcmd :
     Driver driver = DriverFactory.getInstance("author");
System.out.println(driverConfiguration.getAuthenticationHandler()); // 
--> net.webassembletool.authentication.RemoteUserAuthenticationHandler

My extension 'fr.esigate.authentication.CustomUserAuthenticationHandler' 
does not seem to be considered

Here is my driver.properties configuration file :
/author.remoteUrlBase=http://localhost:8080/MagnoliaAuthor///
//author.uriEncoding=UTF-8//
//author.timeout=5000//
//author.useCache=false//
//author.extensions=fr.esigate.authentication.CustomUserAuthenticationHandler/

Thanks
Nicolas TOQUET


Le 06/05/2013 09:39, Francois-Xavier Bonnet a écrit :
> Ok, so you have to write an extension: the extension should detect 
> when you are redirected to the login page, then post the login form 
> and once authenticated send again the original request.
> Maybe we could think of a generic extension for form-based 
> authentication but currently it does not exist.
>
> If you need an example on how to do this, you can have a look at the 
> implementation for CAS SSO:
> http://www.esigate.org/esigate-cas/xref/org/esigate/cas/CasAuthenticationHandler.html
>
> If you decided to write something reusable on other projects, remember 
> that contributions to the project are always welcome.
>
>
> 2013/5/6 <nic...@ne... 
> <mailto:nic...@ne...>>
>
>     Hello,
>
>     It is a form based authentication. The webapp we have to query is
>     Magnolia. There is a public and an author instance. On the Author
>     instance we have to enter credentials when we call a page.
>
>     Thanks
>     Nicolas TOQUET
>
>
>     Le 05/05/2013 22:25, Francois-Xavier Bonnet a écrit :
>>
>>     Hi,
>>
>>     Is it basic authentication or form-based authentication ?
>>     Which version of EsiGate are you using ?
>>
>>     Le 5 mai 2013 18:50, "Nicolas TOQUET"
>>     <nic...@ne...
>>     <mailto:nic...@ne...>> a écrit :
>>
>>         Hello
>>
>>         we try to get the response from a page in an author instance
>>         protected
>>         by login/password.
>>         how can we pass the credential (driver.properties ?)
>>         There is no proxy.
>>
>>         Thanks
>>         Nicolas
>>
>>         ------------------------------------------------------------------------------
>>         Get 100% visibility into Java/.NET code with AppDynamics Lite
>>         It's a free troubleshooting tool designed for production
>>         Get down to code-level detail for bottlenecks, with <2% overhead.
>>         Download for free and get started troubleshooting in minutes.
>>         http://p.sf.net/sfu/appdyn_d2d_ap2
>>         _______________________________________________
>>         Webassembletool-users mailing list
>>         Web...@li...
>>         <mailto:Web...@li...>
>>         https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>>
>
>

Re: [EsiGate-users] credentials

[Nicolas T. <nic...@ne...>]

Hello,

It is a form based authentication. The webapp we have to query is 
Magnolia. There is a public and an author instance. On the Author 
instance we have to enter credentials when we call a page.

Thanks
Nicolas TOQUET


Le 05/05/2013 22:25, Francois-Xavier Bonnet a écrit :
>
> Hi,
>
> Is it basic authentication or form-based authentication ?
> Which version of EsiGate are you using ?
>
> Le 5 mai 2013 18:50, "Nicolas TOQUET" <nic...@ne... 
> <mailto:nic...@ne...>> a écrit :
>
>     Hello
>
>     we try to get the response from a page in an author instance protected
>     by login/password.
>     how can we pass the credential (driver.properties ?)
>     There is no proxy.
>
>     Thanks
>     Nicolas
>
>     ------------------------------------------------------------------------------
>     Get 100% visibility into Java/.NET code with AppDynamics Lite
>     It's a free troubleshooting tool designed for production
>     Get down to code-level detail for bottlenecks, with <2% overhead.
>     Download for free and get started troubleshooting in minutes.
>     http://p.sf.net/sfu/appdyn_d2d_ap2
>     _______________________________________________
>     Webassembletool-users mailing list
>     Web...@li...
>     <mailto:Web...@li...>
>     https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>

Re: [EsiGate-users] credentials

[Francois-Xavier B. <fra...@ce...>]

Ok, so you have to write an extension: the extension should detect when you
are redirected to the login page, then post the login form and once
authenticated send again the original request.
Maybe we could think of a generic extension for form-based authentication
but currently it does not exist.

If you need an example on how to do this, you can have a look at the
implementation for CAS SSO:
http://www.esigate.org/esigate-cas/xref/org/esigate/cas/CasAuthenticationHandler.html

If you decided to write something reusable on other projects, remember that
contributions to the project are always welcome.


2013/5/6 <nic...@ne...>

>  Hello,
>
> It is a form based authentication. The webapp we have to query is
> Magnolia. There is a public and an author instance. On the Author instance
> we have to enter credentials when we call a page.
>
> Thanks
> Nicolas TOQUET
>
>
> Le 05/05/2013 22:25, Francois-Xavier Bonnet a écrit :
>
> Hi,
>
> Is it basic authentication or form-based authentication ?
> Which version of EsiGate are you using ?
>  Le 5 mai 2013 18:50, "Nicolas TOQUET" <nic...@ne...> a
> écrit :
>
>> Hello
>>
>> we try to get the response from a page in an author instance protected
>> by login/password.
>> how can we pass the credential (driver.properties ?)
>> There is no proxy.
>>
>> Thanks
>> Nicolas
>>
>>
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite
>> It's a free troubleshooting tool designed for production
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://p.sf.net/sfu/appdyn_d2d_ap2
>> _______________________________________________
>> Webassembletool-users mailing list
>> Web...@li...
>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>>
>
>

Re: [EsiGate-users] credentials

[Nicolas R. <nic...@gm...>]

Hi Nicolas, 

You can use an authentication handler or an extension (available from esigate 4) :

Basically, add credentials to the request before calling the backend if using HttpAuthentication.  Or POST credentials to a login page, get session then request the target page using the same session.

See : 
http://www.esigate.org/reference.html#Authentication_and_SSO

--
Nicolas


Le 5 mai 2013 à 22:25, Francois-Xavier Bonnet <fra...@ce...> a écrit :

> Hi,
> 
> Is it basic authentication or form-based authentication ?
> Which version of EsiGate are you using ?
> Le 5 mai 2013 18:50, "Nicolas TOQUET" <nic...@ne...> a écrit :
> Hello
> 
> we try to get the response from a page in an author instance protected
> by login/password.
> how can we pass the credential (driver.properties ?)
> There is no proxy.
> 
> Thanks
> Nicolas
> 
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> _______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2_______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users

Re: [EsiGate-users] credentials

[Francois-Xavier B. <fra...@ce...>]

Hi,

Is it basic authentication or form-based authentication ?
Which version of EsiGate are you using ?
 Le 5 mai 2013 18:50, "Nicolas TOQUET" <nic...@ne...> a
écrit :

> Hello
>
> we try to get the response from a page in an author instance protected
> by login/password.
> how can we pass the credential (driver.properties ?)
> There is no proxy.
>
> Thanks
> Nicolas
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> _______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>

[EsiGate-users] credentials

[Nicolas T. <nic...@ne...>]

Hello

we try to get the response from a page in an author instance protected 
by login/password.
how can we pass the credential (driver.properties ?)
There is no proxy.

Thanks
Nicolas

[EsiGate-users] EsiGate 4.0 released !

[François-Xavier B. <fra...@ce...>]

Hi all,

EsiGate 4.0 has just been released on maven central repository. The 
trunk has switched to 5.x for new developments.
This release includes several bug fixes and performance improvements 
related to caching. Several of them were due to Apache HttpClient 
project issues, we have contributed patches that have been included to 
HttpClient 4.2.3

The complete changelog is available here :
https://sourceforge.net/apps/mantisbt/webassembletool/changelog_page.php

FX

[EsiGate-users] EsiGate 4.0-beta-2 released !

[François-Xavier B. <fra...@ce...>]

Hi all,

EsiGate 4.0-beta-2 has just been released on maven central repository. 
The trunk will switch to 5.x for new developments. To ensure 4.0 
stability, there will be no more new development on 4.x branch, only bug 
fixes.

The complete changelog is available here :
https://sourceforge.net/apps/mantisbt/webassembletool/changelog_page.php

FX

Re: [EsiGate-users] Bug sur utilisation esi xpath

[Frederique A. <fre...@sm...>]

Bonjour, 

Pour reproduire l'erreur, il suffit d'ajouter xml:lang="fr" dans le tag <HTML> : 
< html xmlns =" http://www.w3.org/1999/xhtml " xml:lang =" fr "> Puis faire un appel xpath à l'aide de esi:include. 

ESIGate arrive à parser une page ayant des erreurs w3c mineurs (je n'ai pas fait de tests poussés) . 

Je ne pourrait pas fournir de patch avant le 5/11 car je suis en vacances. 

Cdt, 



Aussel Frédérique 
Smile 

----- Mail original -----

De: "Francois-Xavier Bonnet" <fra...@ce...> 
À: "nicolas richeton" <nic...@gm...> 
Cc: "frederique aussel" <fre...@sm...>, web...@li... 
Envoyé: Mercredi 24 Octobre 2012 00:07:51 
Objet: Re: [EsiGate-users] Bug sur utilisation esi xpath 

En principe nu html parser supporte le code malformé et par rapport à d'autres comme htmlparser ou jsoup, je l'avais choisi pour ses performances, le fait qu'il était dispo et mis à jour régulièrement dans le repo central maven et sa capacité à travailler en mode sax plutôt que dom contrairement à la plupart des autres parsers. 


FX 


Le 23 octobre 2012 17:37, < nic...@gm... > a écrit : 



Et sinon, si tu peux donner un test unitaire ou exemple (histoire qu'on ne passe pas 15h à essayer de reproduire :-) ) dans un ticket Mantis, je peux essayer de regarder ma solution avec surcharge de validator.nu . 


Il y a le patch à faire mais plus généralement à voir comment ESIGate se comporte sur du code malformé et si on ne devrait pas utiliser une lib de clean-up HTML avant de parser. 





Nicolas 






Le 23 oct. 2012 à 12:23, François-Xavier Bonnet < fra...@ce... > a écrit : 

<blockquote>

Bonjour, 

Si tu peux soumettre un patch par rapport à la 3.4, on peut imaginer faire une release 3.4.1 
Je me chargerai de reporter le patch dans le trunk pour la version 4. 
Dans ce cas attache ton patch à un ticket Mantis. 



Le 22/10/2012 15:36, fre...@sm... a écrit : 

<blockquote>

Bonjour, 

On utilise la version 3.4 car la 4.0 n'est pas encore validé. 
Est ce que ce sera corrigé dans la 3.4 ? 


Aussel Frédérique 
Smile 



De: "Nicolas Richeton" <nic...@gm...> 
À: "Frederique Aussel" <fre...@sm...> 
Cc: web...@li... 
Envoyé: Samedi 20 Octobre 2012 23:06:59 
Objet: Re: [EsiGate-users] Bug sur utilisation esi xpath 

Bonjour Frédérique, 

De mon coté, je tenterai de surcharger HtmldocumentBuilder / DomTreeBuilder pour injecter le namespace 'xml' qui devrait être présent selon les specs xhtml. Plus intrusif dans validator.nu , mais devrait éviter tout effet de bord. 
On peut aussi combiner avec alter_infoset pour éviter de planter en cas de document invalide. 

Il faut ouvrir un ticket dans mantis :-) 

Nicolas 


Le 19 oct. 2012 à 14:15, Frederique Aussel a écrit : 

> Bonjour, 
> 
> Lorsqu'on utilise esi:include : 
> <esi:include src="$PROVIDER({aggregated2})/block.jsp"xpath="//html:div[@id='xpathfragment']" /> 
> 
> Si la page cible contient dans son tag HTML : xml:lang="fr", ESIGate n'arrive pas à parser le document : 
> 
> org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. 
> at nu.validator.htmlparser.impl.TreeBuilder.fatal(TreeBuilder.java:430) 
> at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:185) 
> at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:44) 
> at nu.validator.htmlparser.impl.TreeBuilder.appendHtmlElementToDocumentAndPush(TreeBuilder.java:4480) 
> at nu.validator.htmlparser.impl.TreeBuilder.startTag(TreeBuilder.java:2534) 
> at nu.validator.htmlparser.impl.Tokenizer.emitCurrentTagToken(Tokenizer.java:1311) 
> at nu.validator.htmlparser.impl.Tokenizer.stateLoop(Tokenizer.java:2152) 
> at nu.validator.htmlparser.impl.Tokenizer.tokenizeBuffer(Tokenizer.java:1522) 
> at nu.validator.htmlparser.io.Driver.runStates(Driver.java:301) 
> at nu.validator.htmlparser.io.Driver.tokenize(Driver.java:217) 
> at nu.validator.htmlparser.dom.HtmlDocumentBuilder.tokenize(HtmlDocumentBuilder.java:405) 
> at nu.validator.htmlparser.dom.HtmlDocumentBuilder.parse(HtmlDocumentBuilder.java:204) 
> at org.esigate.xml.XpathRenderer.render(XpathRenderer.java:69) 
> at org.esigate.Driver.render(Driver.java:300) 
> at org.esigate.Driver.render(Driver.java:254) 
> at org.esigate.esi.IncludeElement.processPage(IncludeElement.java:222) 
> at org.esigate.esi.IncludeElement.parseTag(IncludeElement.java:100) 
> at org.esigate.esi.BaseElement.onTagStart(BaseElement.java:28) 
> at org.esigate.parser.ParserContextImpl.startElement(ParserContextImpl.java:58) 
> at org.esigate.parser.Parser.parse(Parser.java:66) 
> at org.esigate.esi.EsiRenderer.render(EsiRenderer.java:39) 
> at org.esigate.Driver.proxy(Driver.java:358) 
> at org.esigate.servlet.AggregatorServlet.service(AggregatorServlet.java:37) 
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) 
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) 
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) 
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) 
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859) 
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602) 
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) 
> at java.lang.Thread.run(Thread.java:662) 
> Caused by: org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. 
> at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2535) 
> at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.setName(AttrNSImpl.java:113) 
> at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.<init>(AttrNSImpl.java:74) 
> at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:2138) 
> at com.sun.org.apache.xerces.internal.dom.ElementImpl.setAttributeNS(ElementImpl.java:656) 
> at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:179) 
> ... 34 more 
> 
> Est ce que la modification suivante est envisageable dans la classe XpathRenderer : 
> 
> HtmlDocumentBuilder htmlDocumentBuilder = new HtmlDocumentBuilder(XmlViolationPolicy.ALLOW); 
> htmlDocumentBuilder.setNamePolicy(XmlViolationPolicy.ALTER_INFOSET); 
> 
> Les corrections proposées ont pour effet de transformer les attributs non reconnus dans le DOM, avec par exemple pour xml:lang : 
> 
> <html lang="fr" xmlU0003A0lang="fr" xmlns= "http://www.w3.org/1999/xhtml" > 
> 
> Cette correction pourrait induire un effet de bord pour les syntaxes HTML5. 
> 
> Est ce que vous avez une meilleur solution ? 
> 
> Cdt, 
> 
> Aussel Frédérique 
> Smile 
> 
> 
> ------------------------------------------------------------------------------ 
> Everyone hates slow websites. So do we. 
> Make your web apps faster with AppDynamics 
> Download AppDynamics Lite for free today: 
> http://p.sf.net/sfu/appdyn_sfd2d_oct_______________________________________________ 
> Webassembletool-users mailing list 
> Web...@li... 
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users 




------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct 

_______________________________________________
Webassembletool-users mailing list Web...@li... https://lists.sourceforge.net/lists/listinfo/webassembletool-users 



</blockquote>


</blockquote>

Re: [EsiGate-users] Bug sur utilisation esi xpath

[Francois-Xavier B. <fra...@ce...>]

En principe nu html parser supporte le code malformé et par rapport à
d'autres comme htmlparser ou jsoup, je l'avais choisi pour ses
performances, le fait qu'il était dispo et mis à jour régulièrement dans le
repo central maven et sa capacité à travailler en mode sax plutôt que dom
contrairement à la plupart des autres parsers.

FX

Le 23 octobre 2012 17:37, <nic...@gm...> a écrit :

> Et sinon, si tu  peux donner un test unitaire ou exemple (histoire qu'on
> ne passe pas 15h à essayer de reproduire :-) ) dans un ticket Mantis,  je
> peux essayer de regarder ma solution avec surcharge de validator.nu.
>
> Il y a le patch à faire mais plus généralement à voir comment ESIGate se
> comporte sur du code malformé et si on ne devrait pas utiliser une lib de
> clean-up HTML avant de parser.
>
>
> Nicolas
>
>
> Le 23 oct. 2012 à 12:23, François-Xavier Bonnet <
> fra...@ce...> a écrit :
>
>  Bonjour,
>
> Si tu peux soumettre un patch par rapport à la 3.4, on peut imaginer faire
> une release 3.4.1
> Je me chargerai de reporter le patch dans le trunk pour la version 4.
> Dans ce cas attache ton patch à un ticket Mantis.
>
>
> Le 22/10/2012 15:36, fre...@sm... a écrit :
>
> Bonjour,
>
> On utilise la version 3.4 car la 4.0 n'est pas encore validé.
> Est ce que ce sera corrigé dans la 3.4 ?
>
> Aussel Frédérique
> Smile
>
>  ------------------------------
> *De: *"Nicolas Richeton" <nic...@gm...><nic...@gm...>
> *À: *"Frederique Aussel" <fre...@sm...><fre...@sm...>
> *Cc: *web...@li...
> *Envoyé: *Samedi 20 Octobre 2012 23:06:59
> *Objet: *Re: [EsiGate-users] Bug sur utilisation esi xpath
>
> Bonjour Frédérique,
>
> De mon coté, je tenterai  de surcharger HtmldocumentBuilder /
> DomTreeBuilder pour injecter le namespace 'xml' qui devrait être présent
> selon les specs xhtml. Plus intrusif dans validator.nu, mais devrait
> éviter tout effet de bord.
> On peut aussi combiner avec alter_infoset pour éviter de planter en cas de
> document invalide.
>
> Il faut ouvrir un ticket dans mantis :-)
>
> Nicolas
>
>
> Le 19 oct. 2012 à 14:15, Frederique Aussel a écrit :
>
> > Bonjour,
> >
> > Lorsqu'on utilise esi:include :
> > <esi:include
> src="$PROVIDER({aggregated2})/block.jsp"xpath="//html:div[@id='xpathfragment']"
> />
> >
> > Si la page cible contient dans son tag HTML : xml:lang="fr", ESIGate
> n'arrive pas à parser le document :
> >
> > org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or
> change an object in a way which is incorrect with regard to namespaces.
> >       at
> nu.validator.htmlparser.impl.TreeBuilder.fatal(TreeBuilder.java:430)
> >       at
> nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:185)
> >       at
> nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:44)
> >       at
> nu.validator.htmlparser.impl.TreeBuilder.appendHtmlElementToDocumentAndPush(TreeBuilder.java:4480)
> >       at
> nu.validator.htmlparser.impl.TreeBuilder.startTag(TreeBuilder.java:2534)
> >       at
> nu.validator.htmlparser.impl.Tokenizer.emitCurrentTagToken(Tokenizer.java:1311)
> >       at
> nu.validator.htmlparser.impl.Tokenizer.stateLoop(Tokenizer.java:2152)
> >       at
> nu.validator.htmlparser.impl.Tokenizer.tokenizeBuffer(Tokenizer.java:1522)
> >       at nu.validator.htmlparser.io.Driver.runStates(Driver.java:301)
> >       at nu.validator.htmlparser.io.Driver.tokenize(Driver.java:217)
> >       at
> nu.validator.htmlparser.dom.HtmlDocumentBuilder.tokenize(HtmlDocumentBuilder.java:405)
> >       at
> nu.validator.htmlparser.dom.HtmlDocumentBuilder.parse(HtmlDocumentBuilder.java:204)
> >       at org.esigate.xml.XpathRenderer.render(XpathRenderer.java:69)
> >       at org.esigate.Driver.render(Driver.java:300)
> >       at org.esigate.Driver.render(Driver.java:254)
> >       at
> org.esigate.esi.IncludeElement.processPage(IncludeElement.java:222)
> >       at org.esigate.esi.IncludeElement.parseTag(IncludeElement.java:100)
> >       at org.esigate.esi.BaseElement.onTagStart(BaseElement.java:28)
> >       at
> org.esigate.parser.ParserContextImpl.startElement(ParserContextImpl.java:58)
> >       at org.esigate.parser.Parser.parse(Parser.java:66)
> >       at org.esigate.esi.EsiRenderer.render(EsiRenderer.java:39)
> >       at org.esigate.Driver.proxy(Driver.java:358)
> >       at
> org.esigate.servlet.AggregatorServlet.service(AggregatorServlet.java:37)
> >       at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> >       at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> >       at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> >       at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> >       at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> >       at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> >       at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> >       at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> >       at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
> >       at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
> >       at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
> >       at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> >       at java.lang.Thread.run(Thread.java:662)
> > Caused by: org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made
> to create or change an object in a way which is incorrect with regard to
> namespaces.
> >       at
> com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2535)
> >       at
> com.sun.org.apache.xerces.internal.dom.AttrNSImpl.setName(AttrNSImpl.java:113)
> >       at
> com.sun.org.apache.xerces.internal.dom.AttrNSImpl.<init>(AttrNSImpl.java:74)
> >       at
> com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:2138)
> >       at
> com.sun.org.apache.xerces.internal.dom.ElementImpl.setAttributeNS(ElementImpl.java:656)
> >       at
> nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:179)
> >       ... 34 more
> >
> > Est ce que la modification suivante est envisageable dans la classe
> XpathRenderer :
> >
> > HtmlDocumentBuilder htmlDocumentBuilder = new
> HtmlDocumentBuilder(XmlViolationPolicy.ALLOW);
> > htmlDocumentBuilder.setNamePolicy(XmlViolationPolicy.ALTER_INFOSET);
> >
> > Les corrections proposées ont pour effet de transformer les attributs
> non reconnus dans le DOM, avec par exemple pour xml:lang :
> >
> > <html lang="fr" xmlU0003A0lang="fr" xmlns="http://www.w3.org/1999/xhtml"<http://www.w3.org/1999/xhtml>
> >
> >
> > Cette correction pourrait induire un effet de bord pour les syntaxes
> HTML5.
> >
> > Est ce que vous avez une meilleur solution ?
> >
> > Cdt,
> >
> > Aussel Frédérique
> > Smile
> >
> >
> >
> ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> >
> http://p.sf.net/sfu/appdyn_sfd2d_oct_______________________________________________
> > Webassembletool-users mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:http://p.sf.net/sfu/appdyn_sfd2d_oct
>
>
>
> _______________________________________________
> Webassembletool-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>
>
>
>

Re: [EsiGate-users] Bug sur utilisation esi xpath

[Nicolas R. <nic...@gm...>]

Et sinon, si tu  peux donner un test unitaire ou exemple (histoire qu'on ne passe pas 15h à essayer de reproduire :-) ) dans un ticket Mantis,  je peux essayer de regarder ma solution avec surcharge de validator.nu. 

Il y a le patch à faire mais plus généralement à voir comment ESIGate se comporte sur du code malformé et si on ne devrait pas utiliser une lib de clean-up HTML avant de parser.


Nicolas


Le 23 oct. 2012 à 12:23, François-Xavier Bonnet <fra...@ce...> a écrit :

> Bonjour,
> 
> Si tu peux soumettre un patch par rapport à la 3.4, on peut imaginer faire une release 3.4.1
> Je me chargerai de reporter le patch dans le trunk pour la version 4.
> Dans ce cas attache ton patch à un ticket Mantis.
> 
> 
> Le 22/10/2012 15:36, fre...@sm... a écrit :
>> Bonjour,
>> 
>> On utilise la version 3.4 car la 4.0 n'est pas encore validé.
>> Est ce que ce sera corrigé dans la 3.4 ?
>> 
>> Aussel Frédérique 
>> Smile 
>> 
>> De: "Nicolas Richeton" <nic...@gm...>
>> À: "Frederique Aussel" <fre...@sm...>
>> Cc: web...@li...
>> Envoyé: Samedi 20 Octobre 2012 23:06:59
>> Objet: Re: [EsiGate-users] Bug sur utilisation esi xpath
>> 
>> Bonjour Frédérique, 
>> 
>> De mon coté, je tenterai  de surcharger HtmldocumentBuilder / DomTreeBuilder pour injecter le namespace 'xml' qui devrait être présent selon les specs xhtml. Plus intrusif dans validator.nu, mais devrait éviter tout effet de bord.
>> On peut aussi combiner avec alter_infoset pour éviter de planter en cas de document invalide.
>> 
>> Il faut ouvrir un ticket dans mantis :-)
>> 
>> Nicolas 
>> 
>> 
>> Le 19 oct. 2012 à 14:15, Frederique Aussel a écrit :
>> 
>> > Bonjour,
>> > 
>> > Lorsqu'on utilise esi:include :
>> > <esi:include src="$PROVIDER({aggregated2})/block.jsp"xpath="//html:div[@id='xpathfragment']" />
>> > 
>> > Si la page cible contient dans son tag HTML : xml:lang="fr", ESIGate n'arrive pas à parser le document :
>> > 
>> > org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
>> >       at nu.validator.htmlparser.impl.TreeBuilder.fatal(TreeBuilder.java:430)
>> >       at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:185)
>> >       at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:44)
>> >       at nu.validator.htmlparser.impl.TreeBuilder.appendHtmlElementToDocumentAndPush(TreeBuilder.java:4480)
>> >       at nu.validator.htmlparser.impl.TreeBuilder.startTag(TreeBuilder.java:2534)
>> >       at nu.validator.htmlparser.impl.Tokenizer.emitCurrentTagToken(Tokenizer.java:1311)
>> >       at nu.validator.htmlparser.impl.Tokenizer.stateLoop(Tokenizer.java:2152)
>> >       at nu.validator.htmlparser.impl.Tokenizer.tokenizeBuffer(Tokenizer.java:1522)
>> >       at nu.validator.htmlparser.io.Driver.runStates(Driver.java:301)
>> >       at nu.validator.htmlparser.io.Driver.tokenize(Driver.java:217)
>> >       at nu.validator.htmlparser.dom.HtmlDocumentBuilder.tokenize(HtmlDocumentBuilder.java:405)
>> >       at nu.validator.htmlparser.dom.HtmlDocumentBuilder.parse(HtmlDocumentBuilder.java:204)
>> >       at org.esigate.xml.XpathRenderer.render(XpathRenderer.java:69)
>> >       at org.esigate.Driver.render(Driver.java:300)
>> >       at org.esigate.Driver.render(Driver.java:254)
>> >       at org.esigate.esi.IncludeElement.processPage(IncludeElement.java:222)
>> >       at org.esigate.esi.IncludeElement.parseTag(IncludeElement.java:100)
>> >       at org.esigate.esi.BaseElement.onTagStart(BaseElement.java:28)
>> >       at org.esigate.parser.ParserContextImpl.startElement(ParserContextImpl.java:58)
>> >       at org.esigate.parser.Parser.parse(Parser.java:66)
>> >       at org.esigate.esi.EsiRenderer.render(EsiRenderer.java:39)
>> >       at org.esigate.Driver.proxy(Driver.java:358)
>> >       at org.esigate.servlet.AggregatorServlet.service(AggregatorServlet.java:37)
>> >       at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>> >       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>> >       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>> >       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>> >       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>> >       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>> >       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>> >       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>> >       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>> >       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
>> >       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
>> >       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
>> >       at java.lang.Thread.run(Thread.java:662)
>> > Caused by: org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
>> >       at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2535)
>> >       at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.setName(AttrNSImpl.java:113)
>> >       at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.<init>(AttrNSImpl.java:74)
>> >       at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:2138)
>> >       at com.sun.org.apache.xerces.internal.dom.ElementImpl.setAttributeNS(ElementImpl.java:656)
>> >       at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:179)
>> >       ... 34 more
>> > 
>> > Est ce que la modification suivante est envisageable dans la classe XpathRenderer :
>> > 
>> > HtmlDocumentBuilder htmlDocumentBuilder = new HtmlDocumentBuilder(XmlViolationPolicy.ALLOW);
>> > htmlDocumentBuilder.setNamePolicy(XmlViolationPolicy.ALTER_INFOSET);
>> >  
>> > Les corrections proposées ont pour effet de transformer les attributs non reconnus dans le DOM, avec par exemple pour xml:lang :
>> >  
>> > <html lang="fr" xmlU0003A0lang="fr" xmlns="http://www.w3.org/1999/xhtml">
>> > 
>> > Cette correction pourrait induire un effet de bord pour les syntaxes HTML5.
>> > 
>> > Est ce que vous avez une meilleur solution ?
>> > 
>> > Cdt,
>> > 
>> > Aussel Frédérique 
>> > Smile 
>> > 
>> > 
>> > ------------------------------------------------------------------------------
>> > Everyone hates slow websites. So do we.
>> > Make your web apps faster with AppDynamics
>> > Download AppDynamics Lite for free today:
>> > http://p.sf.net/sfu/appdyn_sfd2d_oct_______________________________________________
>> > Webassembletool-users mailing list
>> > Web...@li...
>> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>> 
>> 
>> _______________________________________________
>> Webassembletool-users mailing list
>> Web...@li...
>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users
> 

[EsiGate-users] ESIGate and Siteminder

[Nicolas R. <nic...@gm...>]

Hi all, 

Has anyone used ESIGate or an older WAT version with Siteminder SSO ? (http://www.ca.com/fr/web-access-management.aspx) 
Any feedback ? Especially with authentication on remote application using something similar to CAS Proxy-Granting-Ticket (PGT). 

Thanks, 

Nicolas

Re: [EsiGate-users] Bug sur utilisation esi xpath

[François-Xavier B. <fra...@ce...>]

Bonjour,

Si tu peux soumettre un patch par rapport à la 3.4, on peut imaginer 
faire une release 3.4.1
Je me chargerai de reporter le patch dans le trunk pour la version 4.
Dans ce cas attache ton patch à un ticket Mantis.


Le 22/10/2012 15:36, fre...@sm... a écrit :
> Bonjour,
>
> On utilise la version 3.4 car la 4.0 n'est pas encore validé.
> Est ce que ce sera corrigé dans la 3.4 ?
>
> Aussel Frédérique
> Smile
>
> ------------------------------------------------------------------------
> *De: *"Nicolas Richeton" <nic...@gm...>
> *À: *"Frederique Aussel" <fre...@sm...>
> *Cc: *web...@li...
> *Envoyé: *Samedi 20 Octobre 2012 23:06:59
> *Objet: *Re: [EsiGate-users] Bug sur utilisation esi xpath
>
> Bonjour Frédérique,
>
> De mon coté, je tenterai  de surcharger HtmldocumentBuilder / 
> DomTreeBuilder pour injecter le namespace 'xml' qui devrait être 
> présent selon les specs xhtml. Plus intrusif dans validator.nu, mais 
> devrait éviter tout effet de bord.
> On peut aussi combiner avec alter_infoset pour éviter de planter en 
> cas de document invalide.
>
> Il faut ouvrir un ticket dans mantis :-)
>
> Nicolas
>
>
> Le 19 oct. 2012 à 14:15, Frederique Aussel a écrit :
>
> > Bonjour,
> >
> > Lorsqu'on utilise esi:include :
> > <esi:include 
> src="$PROVIDER({aggregated2})/block.jsp"xpath="//html:div[@id='xpathfragment']" 
> />
> >
> > Si la page cible contient dans son tag HTML : xml:lang="fr", ESIGate 
> n'arrive pas à parser le document :
> >
> > org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to 
> create or change an object in a way which is incorrect with regard to 
> namespaces.
> >       at 
> nu.validator.htmlparser.impl.TreeBuilder.fatal(TreeBuilder.java:430)
> >       at 
> nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:185)
> >       at 
> nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:44)
> >       at 
> nu.validator.htmlparser.impl.TreeBuilder.appendHtmlElementToDocumentAndPush(TreeBuilder.java:4480)
> >       at 
> nu.validator.htmlparser.impl.TreeBuilder.startTag(TreeBuilder.java:2534)
> >       at 
> nu.validator.htmlparser.impl.Tokenizer.emitCurrentTagToken(Tokenizer.java:1311)
> >       at 
> nu.validator.htmlparser.impl.Tokenizer.stateLoop(Tokenizer.java:2152)
> >       at 
> nu.validator.htmlparser.impl.Tokenizer.tokenizeBuffer(Tokenizer.java:1522)
> >       at nu.validator.htmlparser.io.Driver.runStates(Driver.java:301)
> >       at nu.validator.htmlparser.io.Driver.tokenize(Driver.java:217)
> >       at 
> nu.validator.htmlparser.dom.HtmlDocumentBuilder.tokenize(HtmlDocumentBuilder.java:405)
> >       at 
> nu.validator.htmlparser.dom.HtmlDocumentBuilder.parse(HtmlDocumentBuilder.java:204)
> >       at org.esigate.xml.XpathRenderer.render(XpathRenderer.java:69)
> >       at org.esigate.Driver.render(Driver.java:300)
> >       at org.esigate.Driver.render(Driver.java:254)
> >       at 
> org.esigate.esi.IncludeElement.processPage(IncludeElement.java:222)
> >       at 
> org.esigate.esi.IncludeElement.parseTag(IncludeElement.java:100)
> >       at org.esigate.esi.BaseElement.onTagStart(BaseElement.java:28)
> >       at 
> org.esigate.parser.ParserContextImpl.startElement(ParserContextImpl.java:58)
> >       at org.esigate.parser.Parser.parse(Parser.java:66)
> >       at org.esigate.esi.EsiRenderer.render(EsiRenderer.java:39)
> >       at org.esigate.Driver.proxy(Driver.java:358)
> >       at 
> org.esigate.servlet.AggregatorServlet.service(AggregatorServlet.java:37)
> >       at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> >       at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> >       at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> >       at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> >       at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> >       at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> >       at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> >       at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> >       at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
> >       at 
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
> >       at 
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
> >       at 
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> >       at java.lang.Thread.run(Thread.java:662)
> > Caused by: org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is 
> made to create or change an object in a way which is incorrect with 
> regard to namespaces.
> >       at 
> com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2535)
> >       at 
> com.sun.org.apache.xerces.internal.dom.AttrNSImpl.setName(AttrNSImpl.java:113)
> >       at 
> com.sun.org.apache.xerces.internal.dom.AttrNSImpl.<init>(AttrNSImpl.java:74)
> >       at 
> com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:2138)
> >       at 
> com.sun.org.apache.xerces.internal.dom.ElementImpl.setAttributeNS(ElementImpl.java:656)
> >       at 
> nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:179)
> >       ... 34 more
> >
> > Est ce que la modification suivante est envisageable dans la classe 
> XpathRenderer :
> >
> > HtmlDocumentBuilder htmlDocumentBuilder = new 
> HtmlDocumentBuilder(XmlViolationPolicy.ALLOW);
> > htmlDocumentBuilder.setNamePolicy(XmlViolationPolicy.ALTER_INFOSET);
> >
> > Les corrections proposées ont pour effet de transformer les 
> attributs non reconnus dans le DOM, avec par exemple pour xml:lang :
> >
> > <html lang="fr" xmlU0003A0lang="fr" 
> xmlns="http://www.w3.org/1999/xhtml">
> >
> > Cette correction pourrait induire un effet de bord pour les syntaxes 
> HTML5.
> >
> > Est ce que vous avez une meilleur solution ?
> >
> > Cdt,
> >
> > Aussel Frédérique
> > Smile
> >
> >
> > 
> ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> > 
> http://p.sf.net/sfu/appdyn_sfd2d_oct_______________________________________________
> > Webassembletool-users mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
>
>
> _______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users

Re: [EsiGate-users] Bug sur utilisation esi xpath

[Frederique A. <fre...@sm...>]

Bonjour, 

On utilise la version 3.4 car la 4.0 n'est pas encore validé. 
Est ce que ce sera corrigé dans la 3.4 ? 


Aussel Frédérique 
Smile 

----- Mail original -----

De: "Nicolas Richeton" <nic...@gm...> 
À: "Frederique Aussel" <fre...@sm...> 
Cc: web...@li... 
Envoyé: Samedi 20 Octobre 2012 23:06:59 
Objet: Re: [EsiGate-users] Bug sur utilisation esi xpath 

Bonjour Frédérique, 

De mon coté, je tenterai de surcharger HtmldocumentBuilder / DomTreeBuilder pour injecter le namespace 'xml' qui devrait être présent selon les specs xhtml. Plus intrusif dans validator.nu, mais devrait éviter tout effet de bord. 
On peut aussi combiner avec alter_infoset pour éviter de planter en cas de document invalide. 

Il faut ouvrir un ticket dans mantis :-) 

Nicolas 


Le 19 oct. 2012 à 14:15, Frederique Aussel a écrit : 

> Bonjour, 
> 
> Lorsqu'on utilise esi:include : 
> <esi:include src="$PROVIDER({aggregated2})/block.jsp"xpath="//html:div[@id='xpathfragment']" /> 
> 
> Si la page cible contient dans son tag HTML : xml:lang="fr", ESIGate n'arrive pas à parser le document : 
> 
> org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. 
> at nu.validator.htmlparser.impl.TreeBuilder.fatal(TreeBuilder.java:430) 
> at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:185) 
> at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:44) 
> at nu.validator.htmlparser.impl.TreeBuilder.appendHtmlElementToDocumentAndPush(TreeBuilder.java:4480) 
> at nu.validator.htmlparser.impl.TreeBuilder.startTag(TreeBuilder.java:2534) 
> at nu.validator.htmlparser.impl.Tokenizer.emitCurrentTagToken(Tokenizer.java:1311) 
> at nu.validator.htmlparser.impl.Tokenizer.stateLoop(Tokenizer.java:2152) 
> at nu.validator.htmlparser.impl.Tokenizer.tokenizeBuffer(Tokenizer.java:1522) 
> at nu.validator.htmlparser.io.Driver.runStates(Driver.java:301) 
> at nu.validator.htmlparser.io.Driver.tokenize(Driver.java:217) 
> at nu.validator.htmlparser.dom.HtmlDocumentBuilder.tokenize(HtmlDocumentBuilder.java:405) 
> at nu.validator.htmlparser.dom.HtmlDocumentBuilder.parse(HtmlDocumentBuilder.java:204) 
> at org.esigate.xml.XpathRenderer.render(XpathRenderer.java:69) 
> at org.esigate.Driver.render(Driver.java:300) 
> at org.esigate.Driver.render(Driver.java:254) 
> at org.esigate.esi.IncludeElement.processPage(IncludeElement.java:222) 
> at org.esigate.esi.IncludeElement.parseTag(IncludeElement.java:100) 
> at org.esigate.esi.BaseElement.onTagStart(BaseElement.java:28) 
> at org.esigate.parser.ParserContextImpl.startElement(ParserContextImpl.java:58) 
> at org.esigate.parser.Parser.parse(Parser.java:66) 
> at org.esigate.esi.EsiRenderer.render(EsiRenderer.java:39) 
> at org.esigate.Driver.proxy(Driver.java:358) 
> at org.esigate.servlet.AggregatorServlet.service(AggregatorServlet.java:37) 
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) 
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) 
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) 
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) 
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859) 
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602) 
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) 
> at java.lang.Thread.run(Thread.java:662) 
> Caused by: org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. 
> at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2535) 
> at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.setName(AttrNSImpl.java:113) 
> at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.<init>(AttrNSImpl.java:74) 
> at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:2138) 
> at com.sun.org.apache.xerces.internal.dom.ElementImpl.setAttributeNS(ElementImpl.java:656) 
> at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:179) 
> ... 34 more 
> 
> Est ce que la modification suivante est envisageable dans la classe XpathRenderer : 
> 
> HtmlDocumentBuilder htmlDocumentBuilder = new HtmlDocumentBuilder(XmlViolationPolicy.ALLOW); 
> htmlDocumentBuilder.setNamePolicy(XmlViolationPolicy.ALTER_INFOSET); 
> 
> Les corrections proposées ont pour effet de transformer les attributs non reconnus dans le DOM, avec par exemple pour xml:lang : 
> 
> <html lang="fr" xmlU0003A0lang="fr" xmlns="http://www.w3.org/1999/xhtml"> 
> 
> Cette correction pourrait induire un effet de bord pour les syntaxes HTML5. 
> 
> Est ce que vous avez une meilleur solution ? 
> 
> Cdt, 
> 
> Aussel Frédérique 
> Smile 
> 
> 
> ------------------------------------------------------------------------------ 
> Everyone hates slow websites. So do we. 
> Make your web apps faster with AppDynamics 
> Download AppDynamics Lite for free today: 
> http://p.sf.net/sfu/appdyn_sfd2d_oct_______________________________________________ 
> Webassembletool-users mailing list 
> Web...@li... 
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users 

Re: [EsiGate-users] Bug sur utilisation esi xpath

[Nicolas R. <nic...@gm...>]

Bonjour Frédérique, 

De mon coté, je tenterai  de surcharger HtmldocumentBuilder / DomTreeBuilder pour injecter le namespace 'xml' qui devrait être présent selon les specs xhtml. Plus intrusif dans validator.nu, mais devrait éviter tout effet de bord.
On peut aussi combiner avec alter_infoset pour éviter de planter en cas de document invalide.

Il faut ouvrir un ticket dans mantis :-)

Nicolas 


Le 19 oct. 2012 à 14:15, Frederique Aussel a écrit :

> Bonjour,
> 
> Lorsqu'on utilise esi:include :
> <esi:include src="$PROVIDER({aggregated2})/block.jsp"xpath="//html:div[@id='xpathfragment']" />
> 
> Si la page cible contient dans son tag HTML : xml:lang="fr", ESIGate n'arrive pas à parser le document :
> 
> org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
>       at nu.validator.htmlparser.impl.TreeBuilder.fatal(TreeBuilder.java:430)
>       at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:185)
>       at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:44)
>       at nu.validator.htmlparser.impl.TreeBuilder.appendHtmlElementToDocumentAndPush(TreeBuilder.java:4480)
>       at nu.validator.htmlparser.impl.TreeBuilder.startTag(TreeBuilder.java:2534)
>       at nu.validator.htmlparser.impl.Tokenizer.emitCurrentTagToken(Tokenizer.java:1311)
>       at nu.validator.htmlparser.impl.Tokenizer.stateLoop(Tokenizer.java:2152)
>       at nu.validator.htmlparser.impl.Tokenizer.tokenizeBuffer(Tokenizer.java:1522)
>       at nu.validator.htmlparser.io.Driver.runStates(Driver.java:301)
>       at nu.validator.htmlparser.io.Driver.tokenize(Driver.java:217)
>       at nu.validator.htmlparser.dom.HtmlDocumentBuilder.tokenize(HtmlDocumentBuilder.java:405)
>       at nu.validator.htmlparser.dom.HtmlDocumentBuilder.parse(HtmlDocumentBuilder.java:204)
>       at org.esigate.xml.XpathRenderer.render(XpathRenderer.java:69)
>       at org.esigate.Driver.render(Driver.java:300)
>       at org.esigate.Driver.render(Driver.java:254)
>       at org.esigate.esi.IncludeElement.processPage(IncludeElement.java:222)
>       at org.esigate.esi.IncludeElement.parseTag(IncludeElement.java:100)
>       at org.esigate.esi.BaseElement.onTagStart(BaseElement.java:28)
>       at org.esigate.parser.ParserContextImpl.startElement(ParserContextImpl.java:58)
>       at org.esigate.parser.Parser.parse(Parser.java:66)
>       at org.esigate.esi.EsiRenderer.render(EsiRenderer.java:39)
>       at org.esigate.Driver.proxy(Driver.java:358)
>       at org.esigate.servlet.AggregatorServlet.service(AggregatorServlet.java:37)
>       at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
>       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
>       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
>       at java.lang.Thread.run(Thread.java:662)
> Caused by: org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
>       at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2535)
>       at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.setName(AttrNSImpl.java:113)
>       at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.<init>(AttrNSImpl.java:74)
>       at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:2138)
>       at com.sun.org.apache.xerces.internal.dom.ElementImpl.setAttributeNS(ElementImpl.java:656)
>       at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot(DOMTreeBuilder.java:179)
>       ... 34 more
> 
> Est ce que la modification suivante est envisageable dans la classe XpathRenderer :
> 
> HtmlDocumentBuilder htmlDocumentBuilder = new HtmlDocumentBuilder(XmlViolationPolicy.ALLOW);
> htmlDocumentBuilder.setNamePolicy(XmlViolationPolicy.ALTER_INFOSET);
>  
> Les corrections proposées ont pour effet de transformer les attributs non reconnus dans le DOM, avec par exemple pour xml:lang :
>  
> <html lang="fr" xmlU0003A0lang="fr" xmlns="http://www.w3.org/1999/xhtml">
> 
> Cette correction pourrait induire un effet de bord pour les syntaxes HTML5.
> 
> Est ce que vous avez une meilleur solution ?
> 
> Cdt,
> 
> Aussel Frédérique 
> Smile 
> 
> 
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct_______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users

[EsiGate-users] Bug sur utilisation esi xpath

[Frederique A. <fre...@sm...>]

Bonjour, 

Lorsqu'on utilise esi:include : 
< esi:include src="$PROVIDER({ aggregated2 })/block.jsp" xpath="//html:div[@id='xpathfragment']" /> 

Si la page cible contient dans son tag HTML : xml:lang="fr" , ESIGate n'arrive pas à parser le document : 


org.w3c.dom.DOMException : NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. 
at nu.validator.htmlparser.impl.TreeBuilder.fatal( TreeBuilder.java:430 ) 
at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot( DOMTreeBuilder.java:185 ) 
at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot( DOMTreeBuilder.java:44 ) 
at nu.validator.htmlparser.impl.TreeBuilder.appendHtmlElementToDocumentAndPush( TreeBuilder.java:4480 ) 
at nu.validator.htmlparser.impl.TreeBuilder.startTag( TreeBuilder.java:2534 ) 
at nu.validator.htmlparser.impl.Tokenizer.emitCurrentTagToken( Tokenizer.java:1311 ) 
at nu.validator.htmlparser.impl.Tokenizer.stateLoop( Tokenizer.java:2152 ) 
at nu.validator.htmlparser.impl.Tokenizer.tokenizeBuffer( Tokenizer.java:1522 ) 
at nu.validator.htmlparser.io.Driver.runStates( Driver.java:301 ) 
at nu.validator.htmlparser.io.Driver.tokenize( Driver.java:217 ) 
at nu.validator.htmlparser.dom.HtmlDocumentBuilder.tokenize( HtmlDocumentBuilder.java:405 ) 
at nu.validator.htmlparser.dom.HtmlDocumentBuilder.parse( HtmlDocumentBuilder.java:204 ) 
at org.esigate.xml.XpathRenderer.render( XpathRenderer.java:69 ) 
at org.esigate.Driver.render( Driver.java:300 ) 
at org.esigate.Driver.render( Driver.java:254 ) 
at org.esigate.esi.IncludeElement.processPage( IncludeElement.java:222 ) 
at org.esigate.esi.IncludeElement.parseTag( IncludeElement.java:100 ) 
at org.esigate.esi.BaseElement.onTagStart( BaseElement.java:28 ) 
at org.esigate.parser.ParserContextImpl.startElement( ParserContextImpl.java:58 ) 
at org.esigate.parser.Parser.parse( Parser.java:66 ) 
at org.esigate.esi.EsiRenderer.render( EsiRenderer.java:39 ) 
at org.esigate.Driver.proxy( Driver.java:358 ) 
at org.esigate.servlet.AggregatorServlet.service( AggregatorServlet.java:37 ) 
at javax.servlet.http.HttpServlet.service( HttpServlet.java:717 ) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter( ApplicationFilterChain.java:290 ) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter( ApplicationFilterChain.java:206 ) 
at org.apache.catalina.core.StandardWrapperValve.invoke( StandardWrapperValve.java:233 ) 
at org.apache.catalina.core.StandardContextValve.invoke( StandardContextValve.java:191 ) 
at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:127 ) 
at org.apache.catalina.valves.ErrorReportValve.invoke( ErrorReportValve.java:102 ) 
at org.apache.catalina.core.StandardEngineValve.invoke( StandardEngineValve.java:109 ) 
at org.apache.catalina.connector.CoyoteAdapter.service( CoyoteAdapter.java:293 ) 
at org.apache.coyote.http11.Http11Processor.process( Http11Processor.java:859 ) 
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process( Http11Protocol.java:602 ) 
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run( JIoEndpoint.java:489 ) 
at java.lang.Thread.run( Thread.java:662 ) 
Caused by: org.w3c.dom.DOMException : NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. 
at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkDOMNSErr( CoreDocumentImpl.java:2535 ) 
at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.setName( AttrNSImpl.java:113 ) 
at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.<init>( AttrNSImpl.java:74 ) 
at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createAttributeNS( CoreDocumentImpl.java:2138 ) 
at com.sun.org.apache.xerces.internal.dom.ElementImpl.setAttributeNS( ElementImpl.java:656 ) 
at nu.validator.htmlparser.dom.DOMTreeBuilder.createHtmlElementSetAsRoot( DOMTreeBuilder.java:179 ) 
... 34 more 
Est ce que la modification suivante est envisageable dans la classe XpathRenderer : 


HtmlDocumentBuilder htmlDocumentBuilder = new HtmlDocumentBuilder(XmlViolationPolicy. ALLOW ); 
htmlDocumentBuilder.setNamePolicy(XmlViolationPolicy.ALTER_INFOSET); 

Les corrections proposées ont pour effet de transformer les attributs non reconnus dans le DOM, avec par exemple pour xml:lang : 

<html lang="fr" xmlU0003A0lang="fr" xmlns="http://www.w3.org/1999/xhtml"> 
Cette correction pourrait induire un effet de bord pour les syntaxes HTML5. 

Est ce que vous avez une meilleur solution ? 

Cdt, 


Aussel Frédérique 
Smile