Forum Discussion
2 Replies
Sort By
- Michael_JenkinsCirrostratus
In our environment, we use a few subdomains (xyz.example.com, or abc.example.com) and with an iRule have added additional set-cookie headers when the access policy is started to add the session id cookies and specify the domain (domain.com). With this, we get the cookie on that domain as well as any subdomains. Hope this helps (and that I understood your question right).
- Michael_JenkinsCirrostratus
Basically, this is what we are using (though we also have an iRule that intercepts logoff pages to ensure removal of these cookies too). I think we set a variable in access policy completed to check here and do this so you don't have it adding every time, just when the policy completes and the user is logged in.
when HTTP_RESPONSE_RELEASE { Might could use HTTP_RESPONSE instead of HTTP_RESPONSE_RELEASE set sid [ACCESS::session sid] set domaininfo ".[domain [HTTP::host] 2]" Domain needs the prefixed "." HTTP::cookie insert name "MRHSession" value $sid path "/" domain $domain HTTP::cookie insert name "LastMRH_Session" value [substr $sid [expr [string length $sid] - 8]] path "/" domain $domain }