Re: problems with javascript utf-8 with tomcat 4.1.29
Good question. Don't lose hope and try again in esperanto ;^) STOCKHOLM, Raymond wrote: Since I have upgraded to tomcat 4.1.29 (from 4.1.27), my javascript pages containing UTF-8 characters are interpreted as ISO-8859-1 in Mozilla and OPera, but not IE 5.5 My JSP pages are properly declared UTF-8 : %@ page contentType=text/html;charset=UTF-8 pageEncoding=UTF-8 % My HTML page also: meta http-equiv=Content-Type content=text/html; charset=UTF-8 So is my javascript file : script type=text/javascript src=javascript/menu.js charset=UTF-8/script The javascript files are used to contain the translations of the menus, now I have A@ instead of é in my menus... Any ideas ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- *- * Alain Baucant - [EMAIL PROTECTED] *- * Aubay Luxembourg (OFFIS / Aubay-SI) * * Phone: +352 29 92 50 (40) * Fax: +352 29 92 51 * Mobile: +352 021 35 12 81 * * 51, place de Strasbourg * L-2561 LUXEMBOURG * * http://www.aubay.lu *- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to REDIRECT after HTTPS connection failure ?
Thanks for the answer. Bill Barker wrote: Alain Baucant [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hello, my goal: to use httpS with CLIENT and server authentication to connect to tomcat and be able to REDIRECT users who can't identify themselves (can't establish the https connection) with their certificate. If, for any reason (for example: no client certificate) the ssl connection can't be established, how can I redirect the user to another page. You can't really do this without hacking the Tomcat code. I've been meaning to add a clientAuth=want option to the Connector, but haven't gotten around to it yet. I already tried, without succes under httpS, the error-page... declaration in the web.xml The problem seems to be: tomcat doesn't see any error (nothing in the server log file showing the user attempted to connect). And the server doesn't reply to the browser. On a https connection failure : is there any exception tomcat could catch ? Or any other way to redirect the user ? Thanks for your help, Alain Baucant. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- *- * Alain Baucant - [EMAIL PROTECTED] *- * Aubay Luxembourg (OFFIS / Aubay-SI) * * Phone: +352 29 92 50 (40) * Fax: +352 29 92 51 * Mobile: +352 021 35 12 81 * * 51, place de Strasbourg * L-2561 LUXEMBOURG * * http://www.aubay.lu *- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CRL configuration with SSL connector
Is it possible to define a CRL to be checked by tomcat when using SSL ? Thanks for your help, Alain. PS: Where can I find a full description of configuration attributes of the coyote connector ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to REDIRECT after HTTPS connection failure ?
Hello, my goal: to use httpS with CLIENT and server authentication to connect to tomcat and be able to REDIRECT users who can't identify themselves (can't establish the https connection) with their certificate. If, for any reason (for example: no client certificate) the ssl connection can't be established, how can I redirect the user to another page. I already tried, without succes under httpS, the error-page... declaration in the web.xml The problem seems to be: tomcat doesn't see any error (nothing in the server log file showing the user attempted to connect). And the server doesn't reply to the browser. On a https connection failure : is there any exception tomcat could catch ? Or any other way to redirect the user ? Thanks for your help, Alain Baucant. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
