既然選擇了遠方,便只顧風雨兼程.

由于項目需求變更,網(wǎng)絡協(xié)議由之前的http調(diào)整為https. 第一次接觸https,記錄下.
參考相關文檔:
https://blog.csdn.net/u014752325/article/details/73185351
https://blog.csdn.net/u014752325/article/details/73217577
https://blog.csdn.net/guolin_blog/article/details/78179422
OkGo 忽略https證書
OkGo 3.0 文檔上在application初始化中對OKGO的初始化有一種忽略證書驗證的方案:
//方法一:信任所有證書,不安全有風險
HttpsUtils.SSLParams sslParams1 = HttpsUtils.getSslSocketFactory();
//方法二:自定義信任規(guī)則,校驗服務端證書
HttpsUtils.SSLParams sslParams2 = HttpsUtils.getSslSocketFactory(new SafeTrustManager());
//方法三:使用預埋證書,校驗服務端證書(自簽名證書)
HttpsUtils.SSLParams sslParams3 = HttpsUtils.getSslSocketFactory(getAssets().open("srca.cer"));
//方法四:使用bks證書和密碼管理客戶端證書(雙向認證),使用預埋證書,校驗服務端證書(自簽名證書)
HttpsUtils.SSLParams sslParams4 = HttpsUtils.getSslSocketFactory(getAssets().open("xxx.bks"), "123456", getAssets().open("yyy.cer"));
builder.sslSocketFactory(sslParams1.sSLSocketFactory, sslParams1.trustManager);
//配置https的域名匹配規(guī)則,詳細看demo的初始化介紹,不需要就不要加入,使用不當會導致https握手失敗
builder.hostnameVerifier(new SafeHostnameVerifier());
我們只需要加上下面兩行代碼:
//方法一:信任所有證書,不安全有風險
HttpsUtils.SSLParams sslParams1 = HttpsUtils.getSslSocketFactory();
builder.sslSocketFactory(sslParams1.sSLSocketFactory, sslParams1.trustManager);
但是加上以上代碼,項目依舊報錯.
錯誤信息:
Hostname xxx.35.67.xxx not verified:
certificate: sha256/WHR2TrgnZ+qSxokE0kDPeWCzlvkJANKiD2EBzPCltfg=DN: CN=1xxx.35.67.xxx,OU=Unknown,O=Unknown,L=Unknown,ST=Unknown,C=Unknown subjectAltNames: []
意思是我們的請求證書和服務器的證書不一致,在OkHttpClient.Builder 中有一個hostnameVerifier函數(shù),接收一個HostnameVerifier對象
public interface HostnameVerifier {
/**
* Verify that the host name is an acceptable match with
* the server's authentication scheme.
*
* @param hostname the host name
* @param session SSLSession used on the connection to host
* @return true if the host name is acceptable
*/
public boolean verify(String hostname, SSLSession session);
}
該接口作用應該就是驗證證書,成功返回true,反之false.所以我們可以設置驗證證書成功返回true.
okGo忽略Https總結(jié)
在application初始化OKGo的時忽略證書驗證.
第一步:
HttpsUtils.SSLParams sslParams1 = HttpsUtils.getSslSocketFactory();
builder.sslSocketFactory(sslParams1.sSLSocketFactory, sslParams1.trustManager);
第二步:
builder.hostnameVerifier(new HostnameVerifier() {
@Override
public boolean verify(String hostname, SSLSession session) {
//強行返回true 即驗證成功
return true;
}
});
Glide 忽略https證書
由于項目中使用glide加載圖片,雖然網(wǎng)絡接口通了,但是圖片加載失敗.
如果我們想要更改Glide的某些默認配置項,那么我們就需要自定義模塊,自定義模塊功能可以將更改Glide配置,替換Glide組件等操作獨立出來,使得我們能輕松地對Glide的各種配置進行自定義,并且又和Glide的圖片加載邏輯沒有任何交集.
首先我們需要自己定義一個類.并實現(xiàn)GlideModule接口.
public class OkHttpGlideModule implements GlideModule {
@Override
public void applyOptions(Context context, GlideBuilder builder) {
}
@Override
public void registerComponents(Context context, Glide glide) {
}
}
在OkHttpGlideModule類當中,我們重寫了applyOptions()和registerComponents()方法,這兩個方法分別就是用來更改Glide和配置以及替換Glide組件的.不過,現(xiàn)在glide還無法識別OkHttpGlideModule,我們需要在清單文件application 節(jié)點下聲明meta-data 子節(jié)點. name為OkHttpGlideModule,注意必須是全路徑,value 固定寫法 GlideModule.
<application
.....
<meta-data
android:name="xxxx.xxxx.xxx.OkHttpGlideModule"
android:value="GlideModule" />
.....
</application>
glide在底層自己維護一套網(wǎng)絡相關的框架,如果想要使用glide加載https,我們也要做到信任所有證書.
默認情況下,Glide使用的是基于原生HttpURLConnection進行訂制的HTTP通訊組件. 我們可以將HttpURLConnection通訊組件換成OKhttp組件.看一下Glide中目前有哪些組件吧,在Glide類的構(gòu)造方法當中,如下所示:
public class Glide {
Glide(Engine engine, MemoryCache memoryCache, BitmapPool bitmapPool, Context context, DecodeFormat decodeFormat) {
...
register(File.class, ParcelFileDescriptor.class, new FileDescriptorFileLoader.Factory());
register(File.class, InputStream.class, new StreamFileLoader.Factory());
register(int.class, ParcelFileDescriptor.class, new FileDescriptorResourceLoader.Factory());
register(int.class, InputStream.class, new StreamResourceLoader.Factory());
register(Integer.class, ParcelFileDescriptor.class, new FileDescriptorResourceLoader.Factory());
register(Integer.class, InputStream.class, new StreamResourceLoader.Factory());
register(String.class, ParcelFileDescriptor.class, new FileDescriptorStringLoader.Factory());
register(String.class, InputStream.class, new StreamStringLoader.Factory());
register(Uri.class, ParcelFileDescriptor.class, new FileDescriptorUriLoader.Factory());
register(Uri.class, InputStream.class, new StreamUriLoader.Factory());
register(URL.class, InputStream.class, new StreamUrlLoader.Factory());
register(GlideUrl.class, InputStream.class, new HttpUrlGlideUrlLoader.Factory());
register(byte[].class, InputStream.class, new StreamByteArrayLoader.Factory());
...
}
}
可以看到,這里都是以調(diào)用register()方法的方式來注冊一個組件,register()方法中傳入的參數(shù)表示Glide支持使用哪種參數(shù)類型來加載圖片,以及如何去處理這種類型的圖片加載。比如上述register(GlideUrl.class, InputStream.class, new HttpUrlGlideUrlLoader.Factory()); HttpUrlGlideUrlLoader.Factory() 主要負責網(wǎng)絡通訊邏輯, 知道了這點 我們可以在這里解決問題.
創(chuàng)建OkHttpUrlLoader類 其實是按照glide HttpUrlGlideUrlLoader 畫瓢.
public class OkHttpUrlLoader implements ModelLoader<GlideUrl, InputStream> {
public static class Factory implements ModelLoaderFactory<GlideUrl, InputStream> {
private static volatile OkHttpClient internalClient;
private OkHttpClient client;
private static OkHttpClient getInternalClient() {
if (internalClient == null) {
synchronized (Factory.class) {
if (internalClient == null) {
internalClient = new OkHttpClient();
}
}
}
return internalClient;
}
public Factory() {
this(getInternalClient());
}
public Factory(OkHttpClient client) {
this.client = client;
}
@Override
public ModelLoader<GlideUrl, InputStream> build(Context context, GenericLoaderFactory factories) {
return new OkHttpUrlLoader(client);
}
@Override
public void teardown() {
}
}
private final OkHttpClient client;
public OkHttpUrlLoader(OkHttpClient client) {
this.client = client;
}
@Override
public DataFetcher<InputStream> getResourceFetcher(GlideUrl model, int width, int height) {
return new OkHttpStreamFetcher(client, model);
}
}
接著獲取SSLSocketFactory 以及 HostnameVerifier 以便忽略證書
public class SSLSocketClient {
//獲取這個SSLSocketFactory
public static SSLSocketFactory getSSLSocketFactory() {
try {
SSLContext sslContext = SSLContext.getInstance("SSL");
sslContext.init(null, getTrustManager(), new SecureRandom());
return sslContext.getSocketFactory();
} catch (Exception e) {
throw new RuntimeException(e);
}
}
//獲取TrustManager
private static TrustManager[] getTrustManager() {
TrustManager[] trustAllCerts = new TrustManager[]{
new X509TrustManager() {
@Override
public void checkClientTrusted(X509Certificate[] chain, String authType) {
}
@Override
public void checkServerTrusted(X509Certificate[] chain, String authType) {
}
@Override
public X509Certificate[] getAcceptedIssuers() {
return new X509Certificate[]{};
}
}
};
return trustAllCerts;
}
//獲取HostnameVerifier
public static HostnameVerifier getHostnameVerifier() {
HostnameVerifier hostnameVerifier = new HostnameVerifier() {
@Override
public boolean verify(String s, SSLSession sslSession) {
return true;
}
};
return hostnameVerifier;
}
}
好了,現(xiàn)在就只差最后一步,將我們剛剛創(chuàng)建的OkHttpUrlLoader注冊到Glide當中,將原來的HTTP通訊組件給替換掉,如下所示:
public class OkHttpGlideModule implements GlideModule {
@Override
public void applyOptions(Context context, GlideBuilder builder) {
}
@Override
public void registerComponents(Context context, Glide glide) {
OkHttpClient mHttpClient = new OkHttpClient().newBuilder()
.sslSocketFactory(SSLSocketClient.getSSLSocketFactory())
.hostnameVerifier(SSLSocketClient.getHostnameVerifier())
.build();
glide.register(GlideUrl.class, InputStream.class, new OkHttpUrlLoader.Factory(mHttpClient));
}
}
glide忽略Https總結(jié)
主要是替換Glide組件
public class OkHttpGlideModule implements GlideModule {
@Override
public void applyOptions(Context context, GlideBuilder builder) {
}
// 替換組件
@Override
public void registerComponents(Context context, Glide glide) {
// 忽略證書
OkHttpClient mHttpClient = new OkHttpClient().newBuilder()
.sslSocketFactory(SSLSocketClient.getSSLSocketFactory())
.hostnameVerifier(SSLSocketClient.getHostnameVerifier())
.build();
glide.register(GlideUrl.class, InputStream.class, new OkHttpUrlLoader.Factory(mHttpClient));
}
}
public class OkHttpUrlLoader implements ModelLoader<GlideUrl, InputStream> {
public static class Factory implements ModelLoaderFactory<GlideUrl, InputStream> {
private static volatile OkHttpClient internalClient;
private OkHttpClient client;
private static OkHttpClient getInternalClient() {
if (internalClient == null) {
synchronized (Factory.class) {
if (internalClient == null) {
internalClient = new OkHttpClient();
}
}
}
return internalClient;
}
public Factory() {
this(getInternalClient());
}
public Factory(OkHttpClient client) {
this.client = client;
}
@Override
public ModelLoader<GlideUrl, InputStream> build(Context context, GenericLoaderFactory factories) {
return new OkHttpUrlLoader(client);
}
@Override
public void teardown() {
}
}
private final OkHttpClient client;
public OkHttpUrlLoader(OkHttpClient client) {
this.client = client;
}
@Override
public DataFetcher<InputStream> getResourceFetcher(GlideUrl model, int width, int height) {
return new OkHttpStreamFetcher(client, model);
}
}
public class SSLSocketClient {
//獲取這個SSLSocketFactory
public static SSLSocketFactory getSSLSocketFactory() {
try {
SSLContext sslContext = SSLContext.getInstance("SSL");
sslContext.init(null, getTrustManager(), new SecureRandom());
return sslContext.getSocketFactory();
} catch (Exception e) {
throw new RuntimeException(e);
}
}
//獲取TrustManager
private static TrustManager[] getTrustManager() {
TrustManager[] trustAllCerts = new TrustManager[]{
new X509TrustManager() {
@Override
public void checkClientTrusted(X509Certificate[] chain, String authType) {
}
@Override
public void checkServerTrusted(X509Certificate[] chain, String authType) {
}
@Override
public X509Certificate[] getAcceptedIssuers() {
return new X509Certificate[]{};
}
}
};
return trustAllCerts;
}
//獲取HostnameVerifier
public static HostnameVerifier getHostnameVerifier() {
HostnameVerifier hostnameVerifier = new HostnameVerifier() {
@Override
public boolean verify(String s, SSLSession sslSession) {
return true;
}
};
return hostnameVerifier;
}
}
上述三個類可以直接copy到你的項目中,glide 強大之處不僅如此,可以移步郭神
https://blog.csdn.net/sgiceleo/article/details/64440783