CSS cookie insertion

Hi everyone,
I have a question about the cookie insertion.
I understand there are two method of inserting cookie,
1: by Server
2: by CSS
and those method can not be configured simultaneously, that is, if the cookie inserted by server,
CSS can not insert the cookie for the connection.
Because if the cookie inserted by server and by CSS, the server can not accept the cookie
information.
For example,
Server inserts the cookie "0123456789"
and also
CSS inserts the cookie "ARPT=bbbbbbbsssssttttttt"
Server expects the cookie information is "0123456789" but the cookie information reaches
to the server is "ARPT=bbbbbbbsssssttttttt;0123456789".
So the server can not recognize the HTTP connection includes the cookie "ARPT=bbbbbbbsssssttttttt;0123456789"
because the server only understands the cookie "0123456789".
Does my understand is true ?
Or in this situation, does CSS remove the own inserted cookie (ARPT...) by understanding that
"the server also inserts cookie so I (CSS) need to remove cookie" ?
Your information would be greatly appreciated.
Best regards,

just use a different cookie name on the server.
ARPT is the one by default on the CSS and it stands for ARrowPoinT.
If your server uses a different cookie name like SERVER, then both cookie can exist at the same time.
The client would received
ARPT=bbbbbbbsssssttttttt
SERVER=0123456789
and it will also send this data when sending the next request.
The CSS will detect the ARPT=... value and use it and then pass all the data to the server.
The server will also see its own cookie SERVER=.....
Gilles.

Similar Messages

Question on CSS cookie sticky

Hi everyone,
I have a question about CSS cookie sticky.
- Server issues the following cookie string to the client and it is fixed to 18 bytes.
Set-Cookie: JSESSIONID=aaabbbcccdddeeefff; path=/
- Client embedded the following cookie string in the subsequent HTTP header.
Cookie: xx_user_id=ZZZZ03; com.dummy.xyz.session.cookie=|user|pc|ja|Shift_JIS|default||yellow|/oooo/default.portal|; JSESSIONID=aaabbbcccdddeeefff
* Note that I made cookie information suitable as example.
There is the cookie string (JSESSIONID=aaabbbcccdddeeefff) issued by Server in the HTTP header from client but that cookie string (JSESSIONID=aaabbbcccdddeeefff) is located following the cookie string that the client made by oneself at the end of cookie string. And the cookie string and the length of cookie string that client made by oneself might change so the total length of cookie string also might change. It means I can not clarify the total length of the cookie string.
In this situation, I want CSS to stick with cookie string "JSESSIONID=aaabbbcccdddeeefff".
The characters of string located following the "JSESSIONID=" (in this case, "aaabbbcccdddeeefff") might change but it is fixed to 18 bytes. The total length of cookie string is 141 bytes in above mentioned example.
So I informed customer to configure the following parameters to get CSS done cookie sticky for above mentioned cookie string. CSS software version is sg0750303.
owner test
content testsv-tcp80
add service testsv1-tcp80
add service testsv2-tcp80
advanced-balance cookie
　string range 1 to 200
string process-length 18
url "/*"
redundant-index 1001
protocol tcp
port 80
vip address xxx.xxx.xxx.xxx
active
However CSS was not able to treat the above mentioned cookie correctly which means the subsequent HTTP request was not stuck (persisted) to same server.
I do not understand why CSS cookie sticky did not work correctly with this configuration.
Then customer configured CSS with the following parameters to get CSS inserted cookie string and, of course, the result is OK that is CSS could stick the connection to same server.
owner test
content testsv-tcp80
add service testsv1-tcp80
add service testsv2-tcp80
advanced-balance arrowpoint-cookie
url "/*"
redundant-index 1001
protocol tcp
port 80
vip address xxx.xxx.xxx.xxx
active
Has anybody experienced similar thing ?
Could you please let me know if you have any comment, information
Your information would be appreciated.
Best regards,

the CSS does not learn dynamic cookie.
You can match a fixed string inside a cookie and pre-define which server to use with that specific string.
That's why your solution did not work.
Arrowpoint-cookie is a better solution and easier to implement.
Gilles.

CSS Cookie Handling

Anyone know of a way to configure the CSSs to handle dynamic server written cookies? Basically I have two DMZs which are each load balanced with a pair of CSSs. When using arrowpoint cookies on both pairs to keep session, I think one is overwriting the other or it's not writing the second cookie because the CSS cookie (ARPT) already exists. The app servers write a cookie so I could key off that but it's dynamic and I only see how to configure to read other cookies if the content is static. Anyone know how to make the second pair of CSSs write arrowpoint cookies with a different name or how to configure it to read dynamic cookies written by a server? TIA

Well, I was close to finding the answer on my own. Should've spent more time reading and less time posting. LOL
Arrowpoint cookie names can be changed with the "arrowpoint-cookie name" command.
A hash can be run on a cookie as opposed to an absolute value with the "string operation" command.
Cheers!

ACE: new stiky cookie inserted for different URL?

I have sticky cookies set (cookie insert) and http persistence rebalance on. The virtual server is made of a group of three real http servers.
The DNS name of the virtual server is for example "vhost.domain.com".
If I browse (from the internal network) to "http://vhost/" my session is stuck to a real server using cookie stickiness. My question is, when I click a link which is fully qualified e.g. "http://vhost.domain.com/newpage.html" is a stickiness maintained or as the http header has changed is it seen as a new session and potentially sending me to a different real server?

ACE doesn't care about the url.
It will simply look for the presence of the cookie.
If the cookie is there, you will stick to the same rserver.
If not, this is considered a new connection and the request is loadbalanced.
So, it all depends if your browser consider that vhost and vhost.domain.com are the same because the cookie is associated to a domain.
Normally it should consider them the same.
Gilles.

Cookie insert in the CSM module

Hello
I would like to ask if anbody know why when I use the "cookie insert" option in the CSM configuration with the timeout of 60 minutes, from the browser point of view the cookie expires in 2010? I have checked in on the CSM and CSM-S and in both of them it works the same way.
Thanks in advance
Regards
Lukas

Its because of the variable (COOKIE_INSERT_EXPIRATION_DATE) that sets the expiry date to Jan 2010. Use "show mod csm X
variable" to see it.
xyz#sh mod csm 3 var | include EXPIRATION
COOKIE_INSERT_EXPIRATION_DATE Fri, 1 Jan 2010 01:01:50 GMT
Setting this variable to none makes it a session cookie ( expire at
the end of the session -- cookie will be erased when the browser is closed).
(config-module-csm)#variable COOKIE_INSERT_EXPIRATION_DATE ""
With "cookie insert feature" on the CSM ,
the timeout value configured in the sticky has no affect. You will always see a timeout of zero.
Syed Iftekhar Ahmed

ACE Cookie insert behavior

Hi ,
My requirement is as follows
i have following url
http://x.x.x.x/abc
http://x.x.x./dce
http://x.x.x.x/fgh
only for http://x.x.x.x/abc should be using stickiness based on http cookie insert remaining all it should use ip based stickiness.
problem what i am facing is ,
if i access http://x.x.x.x/dce , it is not showing any COOKIE in the header ( which is as expected ) and when i access http://x.x.x./abc it showing the inserted COOKIE (again expected) , but when i am accessing the url http://x.x.x.x/dce or fgh again , it is still showing the INSERTED COOKIE is it a known behaviour?.
as far as i understand , before the session request , ACE maintains the insert cookie values in the cookie database and thus it is less processing intensive.
However , why is it inserting to all request , even though i am not configuring as such .
following is my configuration , is it a known behaviour or is it the way it should work?
serverfarm host SF-FOR-DCE
probe TCP_8032
rserver MYSERVER1 8032
    inservice
rserver MYSERVER2 8032
    inservice
serverfarm host SF-FOR-FGH
probe TCP_8083
rserver MYSERVER1 8083
    inservice
rserver MYSERVER2 8083
    inservice
serverfarm host SF-FOR-ABC
probe TCP_8081
rserver MYSERVER1 8081
    inservice
rserver MYSERVER1 8081
    inservice
sticky http-cookie COOKIE-SKYCHAIN STICKY-ABC
cookie insert browser-expire
timeout 720
replicate sticky
serverfarm SF-FOR-ABC
sticky ip-netmask 255.255.255.0 address source STICKY-DCE
timeout 720
replicate sticky
serverfarm SF-FOR-DCE
sticky ip-netmask 255.255.255.0 address source STICKY-EFG
timeout 720
replicate sticky
serverfarmSF-FOR-FGH
class-map type http loadbalance match-all CM7-1
2 match http url /dce/*.*
class-map type http loadbalance match-all CM7-2
2 match http url /fgh/*.*
class-map type http loadbalance match-all CM7-3
2 match http url /abc*.*
policy-map type loadbalance first-match PM7-1
class CM7-1
    sticky-serverfarm STICKY-DCE
class CM7-2
    sticky-serverfarm STICKY-EFG
class CM7-3
    sticky-serverfarm STICKY-ABC
class-map match-any CM3-VIP
3 match virtual-address x.x.x.x tcp eq www
policy-map multi-match PM34-VIP
class CM3-VIP
    loadbalance vip inservice
    loadbalance policy PM7-1
    loadbalance vip icmp-reply
Assistance appreciated.
thanks
-PMD

Are you seeing the client still send the cookie when going to the other locations /DCE or /FGH, or are you seeing the ACE insert the cookie? If you are only seeing the client still sending the cookie this is expected behavior. The cookie is issued for the path / so if the client learned the cookie from the domain x.x.x.x it will send the cookie any time it goes to that domain regardless of the path that is being used.
Regards
Jim

ACE cookie-insert stickyness

Hi, I am trying to understand the ACE`s cookie-insert method of stickiness. So the ACE will always insert a cookie into the http-header when sending a response to the client/browser. Based on that if it recieves the same cookie-id in the subsequent requests it knows to which end-server to send it as it does an internal hash based on the cookie-value.
My question is, what happens if the server also sends a cookie? Does ACE dis-regards that cookie and inserts a new one on it`s own? How do the cookie-insertion from the server (which is done by default by the web-servers) co-exist with the cookie insertion by the ACE?
thnx

Hi,
As long as they don't both use the Same Cookie name they won't influence each other.
If you don't assign a cookie-name ACE will create a unique one per rserver.
Or you can configure one e.g.
rserver WebServer1 80
cookie-string "ACEWS1Cookie"
More details can be found here:
http://www.cisco.com/en/US/customer/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA3_1_0/configuration/slb/guide/sticky.html

CSM Sticky Cookie Insert

Hello,
We have a Catalyst 6500 w/ CSM-S configuration that has 2 serverfarms with identical real servers using the same VIP. Each farm has 50 real servers (2 IPs with 25 consecutive ports each). One of the serverfarms is defined under a SLB policy with client NAT and the second one directly under the vserver. Both serverfarms are configured with the same sticky group for cookie insert. When I issue "show mod csm 13 sticky group 4" I only see 52 entries instead of 100. Also, some of the entries are duplicate. All the rest of the sticky groups are displaying the correct number of cookie entries, matching the number of real servers in the farms. Any ideas on why this is?

You probably have encountered the following bug fixed only in version 4.2.2
CSCsa74493
CSM: sticky insert table not updated if adding new reals
The workaround is to reboot the CSM or reconfigure reals, policy and vserver in the correct order.
Gilles.

Cookie Insert-Based Persistence

Hi,
I'm slightly confused by the relationship between the various timers with relation to cookies.
For example, I want to use the "cookie insert" feature to provide persistence, but only across sessions. To do this I think I need to modify the COOKIE_INSERT_EXPIRATION_DATE variable to set it to null.
So far so good.
1) do I need to do anything more (like match cookie) to enable this persistence? or does it happen automatically?
2) if I do this what effect does the timer values have on persistence? (i.e. there is a default timeout of 1440 minutes - does this get ignored?)
thanks,
Ray.

setting COOKIE_INSERT_EXPIRATION_DATE to null makes "inserted cookie" session based cookie.
You just need to
1. Define a sticky group with insert cookie
sticky 19 cookie APP1-cookie insert timeout 30
(timeout defined here has no significance, CSM will insert cookie "APP1-cookie" in the server responses.Cookie values will be different for all the reals)
2. And Assign it to a VServer/ policy
vserver APP1-VS
virtual 10.10.10.12 tcp www
serverfarm APP1-SF
sticky 30 group 19
replicate csrp sticky
replicate csrp connection
persistent rebalance
inservice
Syed Iftekhar Ahmed

Bullet style defined as "disc" in CSS is inserted as "circle"

We use RH9 with RSC. I've been wondering about this problem for a few weeks and maybe someone here has an idea why it's happening...
The bullet style is defined as "disc" in our CSS, yet when I insert a bulleted list (using the button on the RH toolbar), my bullets end up as "circle" style. I don't use any other formatting on the bullets (the HTML I get is just <ul style="circle"><li>blahblah</li</ul>). The weird thing is that's it's only happening for me. My coworker opened the same project and she's getting "disc" bullets correctly.
It's not a major problem, I just go in the HTML and fix the bullets manually, but it's really bugging me. Is there a global setting in RH (or Windows?) that I messed up? Did I somehow set "circle" bullets as my default and that's overwriting the CSS?

I am guessing this is not source control related but because of the way you have defined lists.
In older versions of Rh you could define a paragraph style as a list. Since Rh8 lists have to be defined as list styles but you can superimpose a paragraph style for characteristics such as as font size and colour for the text. See Lists on my site and the link to Upgrading.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

How work CodePen (html+css+js) insert Adobe Muse

Hi help me video or image sup please
sory no speak english
how to "link" "codes" insert adobe muse ? thanks all.
http://codepen.io/team/lincolnloop/pen/jEzvBr

You can use Object > Insert HTML for adding your own customized code to the site.
If this is not what you are looking for , please let me know.
Thanks,
Sanjit

CSM inserted cookie - session or persistant

Hi,
I am working on a requirement to load balance http requests to IBM WebSphere Application servers. Each server is configured on the CSM as one real server, but in reality there are several instances of the program running within the server. These instances are fault tolerant, so that if one of them should fail, another instance within the same server can take over and maintain the session. We currently stick clients based on the jsessionid. The problem with this is that if the instance within the server fails and another takes over, it will use a different cookie, and the stickyness is lost. Our requirement is to maintain stickyness to the same real server should an instance of the application fail. We have tried using the HTTP cookie insert feature, but this appears to be a persistant cookie that expires in 2010. We need this to be a session cookie (expires when the client's browser closes). I have seen this URL - http://www.cisco.com/en/US/partner/products/hw/switches/ps708/module_installation_and_configuration_guides_chapter09186a0080463841.html#wp1050708 which states that the CSM-S module will insert a session cookie. I know that the CSM inserts a persistant cookie. Can anyone tell me whether the cookie inserted by the CSM-S module is definitely a session cookie or not. Also, does anyone have any ideas as to how else I can resolve this issue. Many thanks in advance

The browser itself controls if it wants to keep a copy of the cookie for the session only if it want to save it.
The only thing the server, or CSM, can do is set an expiration date.
You can change the expiration to another static date if you think 2010 is too far away.
This is done with a variable.
Do a 'sho mod csm x var' to see which variable it is.
CSM-S is just a CSM with an on-board SSL module. So they act the same in this matter.
Also, even if it was a "session" cookie, I do not see how it would solve your issue.
If the client comes back with no cookie, it will not be sent to another instance of the same server - it will simply be loadbalanced among all the available servers.
What you would need is more like a cookie shared by all instances of the application on a particular server.
Then the CSM could match on the cookie to select a serverfarm that would only use instances running on this server.
Do you have the possibility to insert a static cookie in your application ?
Gilles.

ACE4710 insert cookie - does it overwrite server cookie?

I read the topic
http://docwiki.cisco.com/wiki/Session_Persistence_Using_Cookie_Insert_on_the_Cisco_Application_Control_Engine_Configuration_Example
(great one but unfortunately, doesn't answer my question).
I was trying to implement stickiness based on cookie. Server inserts a cookie and sends it to the browser. I learned from app team that this cookie is changing dynamically during the session, so stickiness based on server’s cookie doesn’t work.
Now I want to investigate into possibility of ACE to insert a cookie. My question is: ACE feature of “cookie insert”: does it add additional cookie into http header without removing server cookies or it deletes the cookie(s) that server put into http header and replaces them with its own cookie?
Thanks!

Hi Dmitriy
If you have different names for server cookie and cookie which ACE is going to insert - server's cookie won't be touched. ACE will just add its own one.

ACE - Load Balance insert cookie method for https

I am trying to load balance between 2 web servers using the cookie insert method by ACE for achieving the session persistence. The servers are not inserting any cookie. It works fine for the http connections but when trying with https connection it is not working.
Can anyone help me with this please.
Is it that ACE cookie insert method of session persistence will not work with https connections.

Hi,
1. for https you can use src ip as sticky (mega proxy problem).
2. you can terminate ssl connection on ace (ssl between client and ace only, between ace and server it's clear) and you can use any L7 sticky (for example cookie)
3. if you need ssl terminate up to real server, you can first terminate ssl between client and ace on ace, then use L7 sticky and after then terminate second ssl to real server.
in other words, if you don't decrypt ssl on ace, you can use only L2/3 data for sticky (or ssl id for ssl v2.0)
martin

Http cookie stickiness

Hi,
I have an http session between Web Server farm and Application Server Farm.
After firt http request, Application Server send this pck (see file http_header.txt ).
So, I configured http cookie Stickiness with Dynamic cookie learning:
sticky http-cookie JSESSIONID Cookie-Bea-Group
cookie offset 0 length 64
timeout 70
timeout activeconns
replicate sticky
serverfarm BEA8-SFARM-3
But it doesn't work. But if web server received an answer from Application server with only one set-cookie
Set-Cookie:JSESSIONID=xxxxx
It work
if in the http header there are two set-cookie doesn't work.
I need stick the session based only on JSESSIONID cookie.
Is it possible and how?
Thanks
Dino

Hi Dear,
The ACE appliance/module has the dynamic cookie feature.
You then just need configure the cookie name and the box does the rest.
When static cookies are used there will only be one entry in the cookie database per real server. So, if ace-cookie is the only cookie defined and there are two servers, there will only be two entries in the sticky database, even if there are thousands of user sessions.
Dynamic cookie learning is another option for keeping the SAP session persistent. The sticky table can hold a maximum of four million dynamic entries (four million simultaneous users). The key is choosing the right cookie name.
Lets take an example of SAP sets a number of cookies for various purposes (note the ace_cookie was set by Cisco ACE using cookie insert, not SAP), but the saplb_* cookie is set by SAP specifically for load-balancers. It has the format saplb_=()[].
Here, the cookie value also helps to verify which server instance and physical node you are connected to.
The configuration process for cookie learning is similar-with a few changes in the syntax.
Example configuration:
ssticky http-cookie saplb_* ep-cookie
replicate sticky
serverfarm EP-HTTP
policy-map type loadbalance http first-match ep-policy
class class-default
sticky-serverfarm ep-cookie
In the above examples, the replicate sticky command is used so that the cookie information is replicated to the standby Cisco ACE context. With this implementation, session persistence is maintained in the event of a failover. The default timeout is one day.
The show sticky data command retrieves the active sticky entries that have been dynamically learned. The value shown is not the actual cookie value, but a function of it created by Cisco ACE.
Example configuration:
switch/SAP-Datacenter# show sticky data
sticky group : ep-cookie
type : HTTP-COOKIE
timeout : 100 timeout-activeconns : FALSE
sticky-entry rserver-instance time-to-expire flags
---------------------+--------------------------------+--------------+-------+
6026630525409626373 SAP-EP:50000 5983
Load Balancing Identifier
The Load Balancing Identifier used for Load balancing to Web AS Java instances has the following syntax.
saplb_=()[]
The cookie is set on path=â/â and domain=.
The same syntax applies if the identifier is used via url rewriting.
The applies only to the J2EE Engine where session stickyness on a process (JVM) level is required. The uniquely identifies a set of instances. If there are no special group definitions then the special group identifier '*' is used. This will be the case for a default installation.
The SAP Web Dispatcher checks for path prefix match and thereby determines group name. This allows to obtain from the set of dispatch cookies or to do initial load balancing for the group. The Java dispatcher receives the request and also checks for the group. The Java dispatcher then reads from the appropriate dispatch cookie or performs initial dispatch on his local nodes.
The CSS does not have the possibility to learn dynamic cookie value created on the server.
So, you can either use arrowpoint cookies which is quite simple or have your server team add a static value to the jsessionid in order to identify the server.
We can then configure the CSS to locate this static value and match it to a service.
If possible kindly rate.
Keep in touch.
Kind regards,
Sachin Garg

CSS cookie insertion

Similar Messages

Maybe you are looking for