SaaS frameworks simplify working with cookies, which are used to establish that two independent requests actually originated from the same user's browser, and can therefore be thought of as part of a session. On the first visit to a site, the server includes a long string (up to 4 KBytes) with the Set-Cookie: HTTP response header. It is the browser's responsibility to include this string with the Cookie: HTTP request header on subsequent requests to that site. The cookie string, which is usually not encrypted but is protected by a "fingerprint" or message authentication code, contains enough information for the server to associate the request with the same user session.

Loading more stuff…

Hmm…it looks like things are taking a while to load. Try again?

Loading videos…