From b8f6599aab367b32e9433c39580f27f7dbdb4f06 Mon Sep 17 00:00:00 2001 From: Akshay Kumar Kodali Date: Tue, 20 Oct 2015 12:31:25 +0530 Subject: [PATCH] Minor language modification --- en/06.2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/06.2.md b/en/06.2.md index 8b386458..d5b9f282 100644 --- a/en/06.2.md +++ b/en/06.2.md @@ -12,7 +12,7 @@ The basic principle behind sessions is that a server maintains information for e The key step here is to send the unique session id to the client. In the context of a standard HTTP response, you can either use the response line, header or body to accomplish this; therefore, we have two ways to send session ids to clients: by cookies or URL rewrites. -- Cookies: the server can easily use `Set-cookie` inside of a response header to save a session id to a client, and a client can then this cookie for future requests; we often set the expiry time for cookies containing session information to 0, which means the cookie will be saved in memory and only deleted after users have close their browsers. +- Cookies: the server can easily use `Set-cookie` inside of a response header to send a session id to a client, and a client can then use this cookie for future requests; we often set the expiry time for cookies containing session information to 0, which means the cookie will be saved in memory and only deleted after users have close their browsers. - URL rewrite: append the session id as arguments in the URL for all pages. This way seems messy, but it's the best choice if clients have disabled cookies in their browsers. ## Use Go to manage sessions