2

I am using a jQuery plug-in to create a cookie (https://github.com/carhartl/jquery-cookie) and have been allowing the cookie to default to a "session cookie". Which is exactly the behavior I would like to have. My concern is that when I deploy my web site to Production, that it will be in a web farm on that environment. Can anyone help me understand what kind of issues, if any, that I will run into with session cookies on a web farm? The version of IIS on the web farm is IIS 7.5.

ADH
  • 2,971
  • 6
  • 34
  • 53
  • What does your session cookie tie to? Meaning, does it have an id that maps to an in memory dictionary, or does it map to a database or cache entry? – David Hoerster Aug 07 '13 at 12:52
  • I am not sure. Should I ask my IIS Administrator? – ADH Aug 07 '13 at 15:05
  • I will look into it, and get back to you. – ADH Aug 07 '13 at 15:23
  • I suspect the session cookie is non-persistent per the following SO posting. http://stackoverflow.com/questions/3737285/set-cookie-to-expire-at-end-of-session-asp-net – ADH Aug 07 '13 at 15:41

1 Answers1

3

No issues at all. Cookies are stored on the client. They don't know or care about your server side infrastructure and how many nodes you have.

There are 2 types of cookies:

  1. Session cookies - live only in the memory of the webbrowser and do not survive browser restart.
  2. Persistent cookies - stored as files on the file system for a specified duration and survive browser restarts.

From the perspective of the server it makes strictly no difference. The cookie will be sent by the client on each request and the node that is serving the request will receive this cookie.

If on the other hand you are storing some information in the memory of the web server, such as for example using ASP.NET Session with the default InProc state then you will have problems. But this has nothing to do with client side cookies.

Darin Dimitrov
  • 1,023,142
  • 271
  • 3,287
  • 2,928