Beka isikhathi sokuphela ku-proxy ye-Apache HttpClient 5 ema ngesikhathi se-CONNECT

I-proxy yamukele i-TCP kodwa ayizange iqede impendulo ye-CONNECT. Impendulo yewebhusayithi ayikaqali; isikhathi esiqondiswe kuphela kuleyo mpendulo yakamuva singashiya lokhu kuhlela kulindile ngaphandle komkhawulo.

Nge-Apache HttpClient 5.3.1, beka okuzenzakalelayo komphathi wokuxhumana:

var connection = ConnectionConfig.custom()
    .setConnectTimeout(Timeout.ofSeconds(5))
    .setSocketTimeout(Timeout.ofSeconds(10))
    .build();

var manager = PoolingHttpClientConnectionManagerBuilder.create()
    .setDefaultConnectionConfig(connection)
    .build();

var client = HttpClients.custom()
    .setConnectionManager(manager)
    .setProxy(new HttpHost("http", "proxy.example", 8080))
    .build();

Sebenzisa amakilasi e-Apache HttpComponents 5 ngaphansi kwe- org.apache.hc, ne- Timeout kuphakethe lomsizi le-core5. Gcina iklayenti emsebenzini wayo bese uyivala. Ukuze kube novivinyo lomphakathi lwe-HTTP olwahlukile, umgijimi ovela ku- uhlu lwama-proxy e-HTTP uhlinzeka ngephuzu lokugcina; gcina indawo ekuyiwa kuyo izinzile uma uqhathanisa izikhathi.

Ngemva kwe-CONNECT, i-TLS ingase idinge umkhawulo wayo wokuhlela ngokusebenzisa ukumiswa kwe-TLS kwe-HttpClient 5. Futhi hlukanisa ukungasebenzi nesikhathi sokugcina sisonke: amabhayithi angena ngokuphazamiseka noma ukushintshana kokuqinisekisa okuphindiwe kungandisa isikhathi sisonke. Sebenzisa inqubomgomo yesikhathi sokugcina noma yokukhansela esekelwa uhlelo lwe- isabelomali esisodwa somsebenzi wonke.