#9108 made it possible for Interceptors to access various OkHttpClient options from Interceptor.Chain.
However, it is not possible to access OkHttpClient.connectionSpecs in this way, as there is no accessor for it.
This presents a problem when implementing "transport" interceptors that wish to take over the Call and run it themselves (as opposed to passing it down OkHttp's stack), which is what we are trying to do. Such an interceptor would want to know what the connection specs so that it can follow them.
@yschimke @vkasprov
#9108 made it possible for Interceptors to access various OkHttpClient options from
Interceptor.Chain.However, it is not possible to access
OkHttpClient.connectionSpecsin this way, as there is no accessor for it.This presents a problem when implementing "transport" interceptors that wish to take over the Call and run it themselves (as opposed to passing it down OkHttp's stack), which is what we are trying to do. Such an interceptor would want to know what the connection specs so that it can follow them.
@yschimke @vkasprov