cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
487
Views
0
Helpful
2
Replies

CSS cookie insertion

snakayama
Level 3
Level 3

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,

1 Accepted Solution

Accepted Solutions

Gilles Dufour
Cisco Employee
Cisco Employee

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.

View solution in original post

2 Replies 2

Gilles Dufour
Cisco Employee
Cisco Employee

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.

Hi,

Thank you very much for your reply.

I understand it.