Session一般是在Web应该中使用的东西,最早我参与的项目都不需要用到Session。但是实际上,很多应用要使用到Session的。
在Web应用中,Session是通过Cookie传递的,在第一次访问网页的时候,如果服务端开启了Session,则在返回信息中会携带Session信息,当之后再访问网页,请求中都会带着Session信息。
用我自己的php服务端展示的话如下所示。
第一次请求,Request中不包含Session信息
GET http://localhost/index/index/index HTTP/1.1
Host: localhost
Connection: keep-alive
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
Accept-Encoding: gzip, deflate, br
Accept-Language: zh-CN,zh;q=0.8
Cookie: pgv_pvi=6689128448; Phpstorm-ba9458cf=5f1ce810-71dc-4a40-821d-4699b7059873
第一次请求后的返回,在set-Cookie中带着Session信息
HTTP/1.1 200 OK
Date: Thu, 31 Aug 2017 03:25:01 GMT
Server: Apache/2.4.23 (Win64) PHP/5.6.25
X-Powered-By: PHP/5.6.25
Set-Cookie: PHPSESSID=t45gjqibrtjsjooe6hlkric6v4; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 566
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html; charset=utf-8
刷新页面后的请求中,就已经带着Session信息了
GET http://localhost/index/index/index HTTP/1.1
Host: localhost
Connection: keep-alive
Cache-Control: max-age=0
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
Accept-Encoding: gzip, deflate, br
Accept-Language: zh-CN,zh;q=0.8
Cookie: pgv_pvi=6689128448; Phpstorm-ba9458cf=5f1ce810-71dc-4a40-821d-4699b7059873; PHPSESSID=t45gjqibrtjsjooe6hlkric6v4
以上关于Session的信息保存和使用(实际是Cookie)都是由浏览器完成的,但是在Android开发的时候,我们没有浏览器帮我们做这些工作,怎么办呢?OKHttp3提供了方便的接口用来对Cookie进行操作。
val okHttpClient = OkHttpClient().newBuilder().cookieJar(object: CookieJar{
val cookieStore = PersistentCookieStore(getApplicationContext())