抽絲剝繭okhttp(五)Interceptors原理
接上文 抽絲剝繭okhttp(四)OkHttpClient原理https://www.jianshu.com/p/62e0b64b8bc6
前面花了很大篇幅我們探明瞭okhttp請求網路的整個流程。感嘆他的科學合理,覺得自己對okhttp算是瞭然於胸了。但是還有更牛逼的(也許是我自己的覺得的牛逼之處),就是他的Interceptor 機制。
Interceptor 機制讓okhttp的擴充性極大地提高,官方的很多功能都是通過interceptor實現的,而且我們自己也可以根據具體業務需要定製自己的interceptor。下面我們先探究一下ok在預設情況下是如何運用interceptor的。
首先我們認識一下Interceptor:
public interface Interceptor {
Response intercept(Chain chain) throws IOException;
interface Chain {
Request request();
Response proceed(Request request) throws IOException;
/**
* Returns the connection the request will be executed on. This is only available in the chains
* of network interceptors; for application interceptors this is always null.
*/
@Nullable Connection connection();
Call call();
int connectTimeoutMillis();
Chain withConnectTimeout(int timeout, TimeUnit unit);
int readTimeoutMillis();
Chain withReadTimeout(int timeout, TimeUnit unit);
int writeTimeoutMillis();
Chain withWriteTimeout(int timeout, TimeUnit unit);
}
}
他內部只有一個方法,就是攔截(intercept),傳入一個他的內部介面(Chain)。在Chain物件中我們可以獲得,Request Response Connection Call 這些在之前過程重要的角色,所以我們在攔截過程中可以操作的東西也是限於這些物件。
Okhttp如何把這些攔截器組裝起來的
關於組裝我們之前的分析中已經說過。在Call物件發起請求動作實際上RealCall物件把自己傳給了整個的攔截器的鏈。原始碼中是這樣體現的。
Response getResponseWithInterceptorChain() throws IOException {
// Build a full stack of interceptors.
List<Interceptor> interceptors = new ArrayList<>();
interceptors.addAll(client.interceptors());//新增okhttpclient中使用者配置的interceptor
interceptors.add(retryAndFollowUpInterceptor);
interceptors.add(new BridgeInterceptor(client.cookieJar()));
interceptors.add(new CacheInterceptor(client.internalCache()));
interceptors.add(new ConnectInterceptor(client));
if (!forWebSocket) {
interceptors.addAll(client.networkInterceptors());
}
interceptors.add(new CallServerInterceptor(forWebSocket));
Interceptor.Chain chain = new RealInterceptorChain(interceptors, null, null, null, 0,
originalRequest, this, eventListener, client.connectTimeoutMillis(),
client.readTimeoutMillis(), client.writeTimeoutMillis());
return chain.proceed(originalRequest);
}
1.okhttp預設會新增一系列的攔截器,本文著重分析這些攔截器的工作流程
2.okhttpClient在builder構建過程中可以新增我們自己的interceptor
public List<Interceptor> interceptors() {
return interceptors;
}
public Builder addInterceptor(Interceptor interceptor) {
if (interceptor == null) throw new IllegalArgumentException("interceptor == null");
interceptors.add(interceptor);
return this;
}
之後會組裝進OkhttpClient中,所以在這裡第一步先把client中的interceptor新增進來。這樣整個攔截器就組裝完畢,,接下來就是一層一層的攔截-處理-傳遞了
interceptors.addAll(client.interceptors());
處理第一步
我們看到上最後一行程式碼是,RealInterceptorChain物件呼叫proceed(originalRequest);所以這裡是整個攔截器啟動的第一步。按常理第一步應該會比較重要;我們進一下看:
@Override
public Response proceed(Request request) throws IOException {
return proceed(request, streamAllocation, httpCodec, connection);
}
public Response proceed(Request request, StreamAllocation streamAllocation, HttpCodec httpCodec,
RealConnection connection) throws IOException {
if (index >= interceptors.size()) throw new AssertionError();
calls++;
// If we already have a stream, confirm that the incoming request will use it.
if (this.httpCodec != null && !this.connection.supportsUrl(request.url())) {
throw new IllegalStateException("network interceptor " + interceptors.get(index - 1)
+ " must retain the same host and port");
}
// If we already have a stream, confirm that this is the only call to chain.proceed().
if (this.httpCodec != null && calls > 1) {
throw new IllegalStateException("network interceptor " + interceptors.get(index - 1)
+ " must call proceed() exactly once");
}
// Call the next interceptor in the chain.
RealInterceptorChain next = new RealInterceptorChain(interceptors, streamAllocation, httpCodec,
connection, index + 1, request, call, eventListener, connectTimeout, readTimeout,
writeTimeout);
Interceptor interceptor = interceptors.get(index);
Response response = interceptor.intercept(next);
// Confirm that the next interceptor made its required call to chain.proceed().
if (httpCodec != null && index + 1 < interceptors.size() && next.calls != 1) {
throw new IllegalStateException("network interceptor " + interceptor
+ " must call proceed() exactly once");
}
// Confirm that the intercepted response isn't null.
if (response == null) {
throw new NullPointerException("interceptor " + interceptor + " returned null");
}
if (response.body() == null) {
throw new IllegalStateException(
"interceptor " + interceptor + " returned a response with no body");
}
return response;
}
在中間部分我們看到關鍵程式碼:
又一次new了一個RealInterceptor 並獲取了第index個interceptor進行處理返回。從這裡我們看到,至少我覺得作者沒有用for迴圈之類的去處理順序呼叫intercept是比我強大的地方。這裡類似遞迴呼叫呼叫到下一層攔截器處理,等下一個處理完了返回來Response給我用。
第一步之後
這裡有多少個攔截器就會遞迴呼叫多少層最後返回來。順便告訴大家這樣的設計模式叫責任鏈模式。我也不會解釋,嘴很笨。畫個圖也許大家就明白了,圖中假設我們沒有自定義的新增interceptor 使用的只有ok內部的幾個。
如圖,我們之前也說個最後一個攔截器發出物理上的網路請求,此前要經過層層處理確保各項功能。所以在這條鏈上我們可以任意的新增我們自己的定義的其他功能的攔截器。只要保證這條鏈的完整暢通,攔截器的設計是非常容易擴充的。一圖勝千言。
如何實現interceptor
從另外一個角度來說擴充性,因為每個interceptor都有自己的功能互不干擾,互相不知道對方的存在,所以也是極大程度上的解耦了。接下來我們分析幾例interceptor的例項。瞭解一下如何自己定義。
HttpLoggingInterceptor
在okhttp的github專案下有一個官方實現的HttpLoggingInterceptor,用來在logcat中列印okhttp請求資訊的攔截器;原始碼地址https://github.com/square/okhttp/blob/master/okhttp-logging-interceptor/src/main/java/okhttp3/logging/HttpLoggingInterceptor.java#L46:20
public final class HttpLoggingInterceptor implements Interceptor {
private static final Charset UTF8 = Charset.forName("UTF-8");
public enum Level {
/** No logs. */
NONE,
/**
* Logs request and response lines.
*
* <p>Example:
* <pre>{@code
* --> POST /greeting http/1.1 (3-byte body)
*
* <-- 200 OK (22ms, 6-byte body)
* }</pre>
*/
BASIC,
/**
* Logs request and response lines and their respective headers.
*
* <p>Example:
* <pre>{@code
* --> POST /greeting http/1.1
* Host: example.com
* Content-Type: plain/text
* Content-Length: 3
* --> END POST
*
* <-- 200 OK (22ms)
* Content-Type: plain/text
* Content-Length: 6
* <-- END HTTP
* }</pre>
*/
HEADERS,
/**
* Logs request and response lines and their respective headers and bodies (if present).
*
* <p>Example:
* <pre>{@code
* --> POST /greeting http/1.1
* Host: example.com
* Content-Type: plain/text
* Content-Length: 3
*
* Hi?
* --> END POST
*
* <-- 200 OK (22ms)
* Content-Type: plain/text
* Content-Length: 6
*
* Hello!
* <-- END HTTP
* }</pre>
*/
BODY
}
public interface Logger {
void log(String message);
/** A {@link Logger} defaults output appropriate for the current platform. */
Logger DEFAULT = new Logger() {
@Override public void log(String message) {
Platform.get().log(INFO, message, null);
}
};
}
public HttpLoggingInterceptor() {
this(Logger.DEFAULT);
}
public HttpLoggingInterceptor(Logger logger) {
this.logger = logger;
}
private final Logger logger;
private volatile Level level = Level.NONE;
/** Change the level at which this interceptor logs. */
public HttpLoggingInterceptor setLevel(Level level) {
if (level == null) throw new NullPointerException("level == null. Use Level.NONE instead.");
this.level = level;
return this;
}
public Level getLevel() {
return level;
}
@Override public Response intercept(Chain chain) throws IOException {
Level level = this.level;
Request request = chain.request();
if (level == Level.NONE) {
return chain.proceed(request);
}
boolean logBody = level == Level.BODY;
boolean logHeaders = logBody || level == Level.HEADERS;
RequestBody requestBody = request.body();
boolean hasRequestBody = requestBody != null;
Connection connection = chain.connection();
String requestStartMessage = "--> "
+ request.method()
+ ' ' + request.url()
+ (connection != null ? " " + connection.protocol() : "");
if (!logHeaders && hasRequestBody) {
requestStartMessage += " (" + requestBody.contentLength() + "-byte body)";
}
logger.log(requestStartMessage);
if (logHeaders) {
if (hasRequestBody) {
// Request body headers are only present when installed as a network interceptor. Force
// them to be included (when available) so there values are known.
if (requestBody.contentType() != null) {
logger.log("Content-Type: " + requestBody.contentType());
}
if (requestBody.contentLength() != -1) {
logger.log("Content-Length: " + requestBody.contentLength());
}
}
Headers headers = request.headers();
for (int i = 0, count = headers.size(); i < count; i++) {
String name = headers.name(i);
// Skip headers from the request body as they are explicitly logged above.
if (!"Content-Type".equalsIgnoreCase(name) && !"Content-Length".equalsIgnoreCase(name)) {
logger.log(name + ": " + headers.value(i));
}
}
if (!logBody || !hasRequestBody) {
logger.log("--> END " + request.method());
} else if (bodyHasUnknownEncoding(request.headers())) {
logger.log("--> END " + request.method() + " (encoded body omitted)");
} else {
Buffer buffer = new Buffer();
requestBody.writeTo(buffer);
Charset charset = UTF8;
MediaType contentType = requestBody.contentType();
if (contentType != null) {
charset = contentType.charset(UTF8);
}
logger.log("");
if (isPlaintext(buffer)) {
logger.log(buffer.readString(charset));
logger.log("--> END " + request.method()
+ " (" + requestBody.contentLength() + "-byte body)");
} else {
logger.log("--> END " + request.method() + " (binary "
+ requestBody.contentLength() + "-byte body omitted)");
}
}
}
long startNs = System.nanoTime();
Response response;
try {
response = chain.proceed(request);
} catch (Exception e) {
logger.log("<-- HTTP FAILED: " + e);
throw e;
}
long tookMs = TimeUnit.NANOSECONDS.toMillis(System.nanoTime() - startNs);
ResponseBody responseBody = response.body();
long contentLength = responseBody.contentLength();
String bodySize = contentLength != -1 ? contentLength + "-byte" : "unknown-length";
logger.log("<-- "
+ response.code()
+ (response.message().isEmpty() ? "" : ' ' + response.message())
+ ' ' + response.request().url()
+ " (" + tookMs + "ms" + (!logHeaders ? ", " + bodySize + " body" : "") + ')');
if (logHeaders) {
Headers headers = response.headers();
for (int i = 0, count = headers.size(); i < count; i++) {
logger.log(headers.name(i) + ": " + headers.value(i));
}
if (!logBody || !HttpHeaders.hasBody(response)) {
logger.log("<-- END HTTP");
} else if (bodyHasUnknownEncoding(response.headers())) {
logger.log("<-- END HTTP (encoded body omitted)");
} else {
BufferedSource source = responseBody.source();
source.request(Long.MAX_VALUE); // Buffer the entire body.
Buffer buffer = source.buffer();
Long gzippedLength = null;
if ("gzip".equalsIgnoreCase(headers.get("Content-Encoding"))) {
gzippedLength = buffer.size();
GzipSource gzippedResponseBody = null;
try {
gzippedResponseBody = new GzipSource(buffer.clone());
buffer = new Buffer();
buffer.writeAll(gzippedResponseBody);
} finally {
if (gzippedResponseBody != null) {
gzippedResponseBody.close();
}
}
}
Charset charset = UTF8;
MediaType contentType = responseBody.contentType();
if (contentType != null) {
charset = contentType.charset(UTF8);
}
if (!isPlaintext(buffer)) {
logger.log("");
logger.log("<-- END HTTP (binary " + buffer.size() + "-byte body omitted)");
return response;
}
if (contentLength != 0) {
logger.log("");
logger.log(buffer.clone().readString(charset));
}
if (gzippedLength != null) {
logger.log("<-- END HTTP (" + buffer.size() + "-byte, "
+ gzippedLength + "-gzipped-byte body)");
} else {
logger.log("<-- END HTTP (" + buffer.size() + "-byte body)");
}
}
}
return response;
}
/**
* Returns true if the body in question probably contains human readable text. Uses a small sample
* of code points to detect unicode control characters commonly used in binary file signatures.
*/
static boolean isPlaintext(Buffer buffer) {
try {
Buffer prefix = new Buffer();
long byteCount = buffer.size() < 64 ? buffer.size() : 64;
buffer.copyTo(prefix, 0, byteCount);
for (int i = 0; i < 16; i++) {
if (prefix.exhausted()) {
break;
}
int codePoint = prefix.readUtf8CodePoint();
if (Character.isISOControl(codePoint) && !Character.isWhitespace(codePoint)) {
return false;
}
}
return true;
} catch (EOFException e) {
return false; // Truncated UTF-8 sequence.
}
}
private boolean bodyHasUnknownEncoding(Headers headers) {
String contentEncoding = headers.get("Content-Encoding");
return contentEncoding != null
&& !contentEncoding.equalsIgnoreCase("identity")
&& !contentEncoding.equalsIgnoreCase("gzip");
}
}
HttpLoggingInterceptor只需要定義兩個成員
level,和Logger,並且會有預設的設定。level決定列印log的級別,Logger決定列印功能的實現。
在intercept中我們看到首先取出chain攜帶的Request物件,並逐一取出 Request物件中的欄位列印出來。
列印完request內容後,通過chain.proceed(request);獲取到了Request物件再逐一列印Request資訊。
全程只做了兩件事,取出物件--》列印物件。很簡單不過。攔截器一般還可以做很多事情來方便我們簡化網路處理,大體上分為三類:
重寫請求、響應
再處理請求、響應
log列印類請求、響應
相關文章
- 抽絲剝繭okhttp(三)Response部分HTTP
- 抽絲剝繭——代理設計模式設計模式
- AbstractQueuedSynchronizer(AQS)抽絲剝繭深入瞭解JUC框架原理AQS框架
- 抽絲剝繭——備忘錄設計模式設計模式
- asyncio系列之抽絲剝繭分析事件排程的核心原理事件
- iOS複雜動畫之抽絲剝繭(Objective C & Swift)iOS動畫ObjectSwift
- [譯] MVVM, Coordinators 和 RxSwift 的抽絲剝繭MVVMSwift
- 記一次公司JVM堆溢位抽絲剝繭定位的過程JVM
- 抽絲剝繭 – 例項簡析重構程式碼的三板斧
- 技術抽絲剝繭|為什麼 Redis 內部使用不同編碼?Redis
- 記一次公司JVM堆溢位抽繭剝絲定位的過程JVM
- 手把手教你擼出跑男動畫 CSS3-Animation抽絲剝繭動畫CSSS3
- 轉貼老熊_抽絲剝繭分析處理oracle rac crs安裝故障Oracle
- Python <演算法思想集結>之抽絲剝繭聊動態規劃Python演算法動態規劃
- 就2小時教會你抽絲剝繭CAAnimation核心動畫之精美的下載動畫動畫
- 一文抽絲剝繭帶你掌握複雜Gremlin查詢的除錯方法REM除錯
- 又一起.NET程式掛死, 用 Windbg 抽絲剝繭式的真實案例分析
- OkHttp - Interceptors(三)HTTP
- OkHttp Interceptors(四)HTTP
- 抽絲剝繭:詳述一次DevServer Proxy配置無效問題的細緻排查過程devServer
- OkHttp3深入瞭解之InterceptorsHTTP
- spring mvc interceptorsSpringMVC
- 商務部:2019年中國繭絲綢行業發展報告行業
- OkHttp原理解析1(框架流程篇)HTTP框架
- OKHttp網路請求原理流程解析HTTP
- OkHttp 3.7原始碼分析(五)——連線池HTTP原始碼
- 2022年三季度全國繭絲綢行業景氣調查行業
- 常用輪子之Okhttp基本使用及原理HTTP
- OkHttp 原始碼剖析系列(五)——代理路由選擇HTTP原始碼路由
- 【抽五分鐘】使用VuePress建立線上文件中心Vue
- C# 12 攔截器 InterceptorsC#
- 深入剖析OkHttp系列(五) 來自官方的事件機制HTTP事件
- 300 萬粉絲的祕密:微信抽獎活動從架構到運營架構
- [搞定開源] 第一篇 okhttp 3.10原理HTTP
- okhttpHTTP
- Android OkHttp(一)原始碼出發探尋執行原理AndroidHTTP原始碼
- 51nod 1103 N的倍數 (抽屜原理)
- SSL剝離工具sslstrip