You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Jason Novotny <ja...@gmail.com> on 2014/11/12 22:40:32 UTC
wicket + jsessionid and 302 issues
Hi wicketeers,
I was hoping to get rid of the jsessionid that appears in the
browsewr bar when running my wicket app under Tomcat 7, and I added the
following to web.xml:
<session-config>
<session-timeout>30</session-timeout>
<tracking-mode>COOKIE</tracking-mode>
</session-config>
However, now in production we get all these 302 redirects which are
causing an infinite recursion. What is the best way to handle this? I
also found a wiki page
https://cwiki.apache.org/confluence/display/WICKET/SEO+-+Search+Engine+Optimization
but wasn't sure if this also applied to using Wicket 6.
Thanks, Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: wicket + jsessionid and 302 issues
Posted by Wayne W <wa...@gmail.com>.
Perhaps your tomcats are not getting the session id? make sure your apache
is passing the JSESSION to the tomcat instance
ie ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=Off
On Thu, Nov 13, 2014 at 12:37 AM, Jason Novotny <ja...@gmail.com>
wrote:
> Hi,
>
> I figured more detailed config info would be helpful. I want my production
> app to be accessible via https only. The connection is SSL to our Apache
> load balancer which is then http to our Tomcat7 instance.
> The Tomcat 7 connector is default:
>
> <Connector port="8080" protocol="HTTP/1.1"
> connectionTimeout="20000"
> redirectPort="8443" />
>
> Just not sure how to config the web.xml or if my tomcat config needs
> changing.
>
> Thanks, Jason
>
>
> On 11/12/14, 1:40 PM, Jason Novotny wrote:
>
>> Hi wicketeers,
>>
>> I was hoping to get rid of the jsessionid that appears in the
>> browsewr bar when running my wicket app under Tomcat 7, and I added the
>> following to web.xml:
>>
>> <session-config>
>> <session-timeout>30</session-timeout>
>> <tracking-mode>COOKIE</tracking-mode>
>> </session-config>
>>
>> However, now in production we get all these 302 redirects which are
>> causing an infinite recursion. What is the best way to handle this? I also
>> found a wiki page https://cwiki.apache.org/confluence/display/WICKET/SEO+
>> -+Search+Engine+Optimization but wasn't sure if this also applied to
>> using Wicket 6.
>>
>> Thanks, Jason
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: wicket + jsessionid and 302 issues
Posted by Jason Novotny <ja...@gmail.com>.
Hi,
I figured more detailed config info would be helpful. I want my
production app to be accessible via https only. The connection is SSL to
our Apache load balancer which is then http to our Tomcat7 instance.
The Tomcat 7 connector is default:
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" />
Just not sure how to config the web.xml or if my tomcat config needs
changing.
Thanks, Jason
On 11/12/14, 1:40 PM, Jason Novotny wrote:
> Hi wicketeers,
>
> I was hoping to get rid of the jsessionid that appears in the
> browsewr bar when running my wicket app under Tomcat 7, and I added
> the following to web.xml:
>
> <session-config>
> <session-timeout>30</session-timeout>
> <tracking-mode>COOKIE</tracking-mode>
> </session-config>
>
> However, now in production we get all these 302 redirects which are
> causing an infinite recursion. What is the best way to handle this? I
> also found a wiki page
> https://cwiki.apache.org/confluence/display/WICKET/SEO+-+Search+Engine+Optimization
> but wasn't sure if this also applied to using Wicket 6.
>
> Thanks, Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org