If you are directing from HTTP to HTTPS or vise versa, then there would be possible change of session ID. AFAIKR, it is due to a tomcat setting. Further, if you are not sending Cookie header with a request, then server will generate a new cookie and send to the browser. Other than those, I don't think Jaggery has anything to do with this.
Anyway, if you can meet me tomorrow, I can help you to figure it out. /Ruchira On Tue, Apr 1, 2014 at 5:43 PM, Rajith Vitharana <[email protected]> wrote: > Hi all, > > When I have redirected from from one of my jaggery page to another jaggery > page( using response.redirect("......) method) sessionId gets changed in > server side. Any idea why that happens? > > Thanks > > -- > Rajith Vitharana > > Software Engineer, > WSO2 Inc. : wso2.com > Mobile : +94715883223 > Blog : http://lankavitharana.blogspot.com/ > -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>* *email: [email protected] <[email protected]>, blog: ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, mobile: +94 77 5493444*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
