From afb29a85d9bb0bd3bbb7cfa66fb75e8d485def89 Mon Sep 17 00:00:00 2001 From: Jimmy99 Date: Wed, 6 Apr 2016 11:12:48 +0200 Subject: [PATCH] Update 06.5.md typographical errors and improved readability --- en/06.5.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/06.5.md b/en/06.5.md index 45281518..027d1d14 100644 --- a/en/06.5.md +++ b/en/06.5.md @@ -1,6 +1,6 @@ # 6.5 Summary -In this chapter, we learned about the definition and purpose of sessions and cookies, and the relationship between the two. Since Go doesn't support sessions in its standard library, we also designed our own session manager. We went through the everything from creating client sessions to deleting them. We then defined an interface called `Provider` which supports all session storage structures. In section 6.3, we implemented a memory based session manager to persist client data across sessions. In section 6.4, I show you one way of hijacking a session. Then we looked at how to prevent your own sessions from being hijacked. I hope that you now understand most of the working principles behind sessions so that you're able to safely use them in your applications. +In this chapter, we learned about the definition and purpose of sessions and cookies, and the relationship between the two. Since Go doesn't support sessions in its standard library, we also designed our own session manager. We went through everything from creating client sessions to deleting them. We then defined an interface called `Provider` which supports all session storage structures. In section 6.3, we implemented a memory based session manager to persist client data across sessions. In section 6.4, I demonstrated one way of hijacking a session. Then we looked at how to prevent your own sessions from being hijacked. I hope that you now understand most of the working principles behind sessions so that you're able to safely use them in your applications. ## Links