Session cookies with load balancing (Not sticky sessions)
===

I have scanned RFC 6265 but did not find the answer to the following.

I want to put a naive round-robbin load-balancer in front of multiple servers for a single webapp.  The load-balancer does *not* provide sticky sessions.  So a client will typically bounce from one appserver to another on successive requests.  

On the first connection, the client has no SID and is randomly routed to, say, server A.  
Server A responds with a session cookie, a nonce.

On the next connection, the client includes the SID from server A in the HTTP headers.
This time the client is randomly routed to, say, server B.
Server B sees the SID which (one hopes!) does not match any SID it has issued.
What happens?  Does server B just ignore the "bad" SID, or complain, or ignore the request, or what?

The idea is, I don't want to use session cookies at all.  I want to avoid all the complexities of stickiness.  But I also know that my servers will probably generate -- and more to the point look for -- session cookies anyway.  

How can I make sure that the servers just ignore (or better yet not set) session cookies?

