Re: Best practice to programmatically get the disableURLRewriting context attribute value

2014-04-22 Thread lo lo
I will use a filter to remove and prevent the jsessionid in the URL. It's indeed really simpler! Thanks for your answer and your suggestions. Lo 2014-04-18 22:41 GMT+02:00 Christopher Schultz ch...@christopherschultz.net : -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Lo, On

Re: Best practice to programmatically get the disableURLRewriting context attribute value

2014-04-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Lo, On 4/17/14, 10:44 AM, Sauvel Laurent wrote: 1. Before testing the code below with different Tomcat configurations, I would like to know if there is a better way to do what I want. I'm not really satisfied with this code that is closely

Re: Best practice to programmatically get the disableURLRewriting context attribute value

2014-04-17 Thread Mark Thomas
On 10/04/2014 14:01, lo lo wrote: Tomcat version 6.0.x on Linux OS Hi all, I have an application deployed on several customers Tomcat servers. The Tomcat versions are different (6.0.16, 6.0.37, etc.) and asking all customers to upgrade to the latest Tomcat version would be too tricky.

RE: Best practice to programmatically get the disableURLRewriting context attribute value

2014-04-17 Thread Sauvel Laurent
in the URL Lo -Message d'origine- De : Mark Thomas [mailto:ma...@apache.org] Envoyé : jeudi 17 avril 2014 11:54 À : Tomcat Users List Objet : Re: Best practice to programmatically get the disableURLRewriting context attribute value On 10/04/2014 14:01, lo lo wrote: Tomcat version 6.0.x