Hello,
I tried copying all cookies from the HTTP request to HTTP response and
it seemed to have a positive effect (unless our hosting company fixed
something on their load balancer). However, I would expect Wicket to
copy cookies from request to response by default, is this true?
Here is the
one does not need to copy cookies because browsers retain them across requests.
-igor
On Sat, Apr 30, 2011 at 5:01 PM, Alec Swan alecs...@gmail.com wrote:
Hello,
I tried copying all cookies from the HTTP request to HTTP response and
it seemed to have a positive effect (unless our hosting
Even if the next request is made from inside an IFrame? If so, is this
problem definitely a problem with the load balancer setup?
Our hosting company ran HTTP trace and said this:
Customer connects to the cluster via HTTP, in this case they are routed to
web2.
This packet passes through the
this is because cookies created in http are not transferred to https
and viceversa afair. i think this can be changed by turning off secure
cookies in tomcat or something like that.
-igor
On Sat, Apr 30, 2011 at 6:06 PM, Alec Swan alecs...@gmail.com wrote:
Even if the next request is made from
Thank you for the great hint! It seems like a lot of people have a
problem JSESSIONID cookie being lost by Tomcat when switching from
HTTPS to HTTP. We are switching in the opposite direction, but I
assume the could be problematic as well.
At this point we are willing to force HTTPS for the
or just put @requireshttps on your base page
-igor
On Sat, Apr 30, 2011 at 6:49 PM, Alec Swan alecs...@gmail.com wrote:
Thank you for the great hint! It seems like a lot of people have a
problem JSESSIONID cookie being lost by Tomcat when switching from
HTTPS to HTTP. We are switching in the
Hello,
We just put our webapp behind a load balancer with sticky sessions.
After that we started noticing that load balancer cookie gets lost
when a modal window is popped up by a link click. Here is the code we
use to display the modal window:
new AjaxLink(editLink)
{
