From d48f9cd5f9cfac621dfab98c6c0fa18e8204c75a Mon Sep 17 00:00:00 2001 From: Aishraj Dahal Date: Wed, 29 Apr 2015 19:23:53 +0530 Subject: [PATCH] Removed redundant word --- 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 0bbb6bdf..8b386458 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 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 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. - 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