v10 cookie insert problem

I guess I've never seen more than one Cookie header.

 

 

IIS is showing it as one cookie in the log with a comma as the separator.

 

 

When we ask for the cookie value in ASP.NET, it's giving us the cookie we want plus the appended cookie since it immediately follows the one we want. We get back from code what I included in my first post...everything after the name TFSessionId through the end minus the last semi-colon. I don't know why ASP.NET is giving us all that if you're saying that it's normal to have more than one Cookie header.

 

 

I think I'm missing something, but if when using the built in cookie objects in ASP.NET it stumbles over the 2nd cookie header, why would someone use the "HTTP::cookie insert" command?

 

 

I think I'm going to re-work the iRule to pull the cookie header and use string commands to rip it apart and rebuild it with my needed additions (if I can't find a matching cookie in the string) and then replace the cookie header with a new one. I have a feeling this is goin to chew up Big-IP processing, but I don't see how using the built-in cookie command is safe...