上篇 我们了解了下OkHttp的重连机制(RetryAndFollowUpInterceptor),此处我们来看下他的下一级拦截器。BridgeInterceptor。从名字我们已经差不多已经了解了它一半---桥接器。嘿嘿,那就来看下代码验证下吧。
public Response intercept(Chain chain) throws IOException {
Request userRequest = chain.request();
Builder requestBuilder = userRequest.newBuilder();
RequestBody body = userRequest.body();
if (body != null) { // body的content配置
MediaType contentType = body.contentType();
if (contentType != null) {
requestBuilder.header("Content-Type", contentType.toString());
}
long contentLength = body.contentLength();
if (contentLength != -1L) {
requestBuilder.header("Content-Length", Long.toString(contentLength));
requestBuilder.removeHeader("Transfer-Encoding"); 主体的编码格式
} else {
requestBuilder.header("Transfer-Encoding", "chunked");
requestBuilder.removeHeader("Content-Length");
}
}
// host自动填充
if (userRequest.header("Host") == null) {
requestBuilder.header("Host", Util.hostHeader(userRequest.url(), false));
}
// connection添加默认值
if (userRequest.header("Connection") == null) {
requestBuilder.header("Connection", "Keep-Alive");
}
boolean transparentGzip = false;
if (userRequest.header("Accept-Encoding") == null && userRequest.header("Range") == null) {
transparentGzip = true;
requestBuilder.header("Accept-Encoding", "gzip");
}
List<Cookie> cookies = this.cookieJar.loadForRequest(userRequest.url());
if (!cookies.isEmpty()) {
requestBuilder.header("Cookie", this.cookieHeader(cookies));
}
if (userRequest.header("User-Agent") == null) {
requestBuilder.header("User-Agent", Version.userAgent());
}
Response networkResponse = chain.proceed(requestBuilder.build());
// 接口成功时更新配置及body转换等操作
HttpHeaders.receiveHeaders(this.cookieJar, userRequest.url(), networkResponse.headers());
okhttp3.Response.Builder responseBuilder = networkResponse.newBuilder().request(userRequest);
if (transparentGzip && "gzip".equalsIgnoreCase(networkResponse.header("Content-Encoding")) && HttpHeaders.hasBody(networkResponse)) {
GzipSource responseBody = new GzipSource(networkResponse.body().source());
Headers strippedHeaders = networkResponse.headers().newBuilder().removeAll("Content-Encoding").removeAll("Content-Length").build();
responseBuilder.headers(strippedHeaders);
responseBuilder.body(new RealResponseBody(strippedHeaders, Okio.buffer(responseBody)));
}
return responseBuilder.build();
}
可以看到,以Chain的proceed方法为分界点,上为:处理一些header信息,把header信息转为http协议可用的header,也就是完善了请求信息,让服务器能正确识别,配置完成后开始往往下执行。下为:在责任链返回结果后如果服务器进行了gzip压缩则继续okio进行解压并重新生成下Respose的标题和主体。类如其名-做为一个牵线的替代者。
关于header这里借用大神的一张表格标示图,原地址点这里
字段名 | 含义 |
---|---|
Content-Type | 实体主体的媒体类型 |
Content-Length | 实体主体的大小(单位:字节) |
Transfer-Encoding | 指定报文主体的传输编码方式 |
Host | 客户端指定想访问的http服务器的域名/IP和端口号 |
Connection | 当client和server通信时对于长链接如何进行处理 |
Accept-Encoding | 优先的内容编码 |
Range | 实体的字节范围 |
Cookie | 设置cookies |
User-Agent | HTTP客户端程序的信息 |