AW: 2 different context paths using one single war file

Hi, as Martin suggested, a proxy is the best solution for this. If you don't want to setup a proxy perhaps this could fit your needs: Deploy your application as ROOT.war in Tomcat. Then you could use the following URLs: http://hostname/page1 http://hostname/page2 Regards, Thomas -Ursprü

AW: 2 different context paths using one single war file

://tomcat.apache.org/tomcat-8.0-doc/config/context.html Regards, Thomas -Ursprüngliche Nachricht- Von: Thomas Rohde Gesendet: Freitag, 9. Oktober 2015 09:22 An: users@wicket.apache.org Betreff: AW: 2 different context paths using one single war file Hi, as Martin suggested, a proxy is the best solution

AW: IP Authentication

Hi Lon! What about using the container features for this? If you are using Tomcat you could add a RemoteAdressValve (https://tomcat.apache.org/tomcat-8.5-doc/config/valve.html#Remote_Address_Valve). Example: The allow attribute needs a regular expression with the ip adresses from your whitel

Wicket Session ID and Tomcat Session ID not equal

Hi Wicket users, we are using Wicket 1.4.19 with Tomcat 7.0.21 and we observered a curious behavior. If we log the Session ID we get two different ID's. HttpSession httpSession = ((ServletWebRequest) RequestCycle.get().getRequest()).getHttpServletRequest().getSession(false); The value of 'WebS

Wicket session id not up to date due to Tomcat session fixation protection

Hi! We are using Wicket 1.4.20 and Tomcat 7.0.21. After form based authentication (configured in web.xml) we call wicketSession.replaceSession() in the constructor of our base page and send a redirect to our welcome page. Due to tomcat's session fixation protection the session id changes for s

AW: Wicket session id not up to date due to Tomcat session fixation protection

) > > On Wed, Apr 4, 2012 at 9:27 AM, Thomas Rohde wrote: > > Hi! > > > > We are using Wicket 1.4.20 and Tomcat 7.0.21. > > > > After form based authentication (configured in web.xml) we call > wicketSession.replaceSession() in the constructor of our base

AW: Wicket session id not up to date due to Tomcat session fixation protection

ed, Apr 4, 2012 at 10:18 AM, Thomas Rohde wrote: > > Hi Martin, > > > > but the AbstractHttpSesionStore has a SessionBindingListener which stores > > the > session id and the Session class has an id member variable. > > This is improved in 6.x and the sessi

AW: Wicket session id not up to date due to Tomcat session fixation protection

true); > idField.set(this, null); > > I.e. null-ify the cached session id in Session. > > > On Wed, Apr 4, 2012 at 10:57 AM, Thomas Rohde wrote: > > Hi Martin, > > > > see inline. > > > > Thanks! > > Thomas > > > > -Ursprünglich

AW: Wicket session id not up to date due to Tomcat session fixation protection

det: Mi 04.04.2012 11:43 Betreff:Re: Wicket session id not up to date due to Tomcat session fixation protection An: users@wicket.apache.org; > Sorry. > I didn't understand you. > > A quickstart will make it easier for me to help you. > > On Wed, Apr 4, 20

AW: Wicket session id not up to date due to Tomcat session fixation protection

omcat session fixation protection An: users@wicket.apache.org; > With a quickstart I'll be more certain what exactly happens and how to > solve it the best way... > Until then use this solution since it works for you. > > On Wed, Apr 4, 2012 at 12:11 PM, Thomas Rohde