Sa ClientResource na Restlet ya yi amfani da hanyar proxy ɗin da ka saita

Saitaccen Client ba ya da wani tasiri a kan ClientResource da har yanzu ke amfani da wata hanyar daban. Ga mataimakin org.restlet.ext.httpclient na Restlet 2.4.4, haɗa albarkar da wannan abokin ciniki kafin ka fara shi:

Client connector = new Client(new Context(), Protocol.HTTPS);
connector.getContext().getParameters().set("proxyHost", "proxy.example");
connector.getContext().getParameters().set("proxyPort", "8080");

ClientResource resource = new ClientResource(
    "https://service.example/status");
resource.setNext(connector);
connector.start();
try {
    String body = resource.get().getText();
} finally {
    resource.release();
    connector.stop();
}

setNext(connector) ita ce wurin haɗawa. Mahalli yana amfani da maɓallan da aka rubuta na mataimakin proxyHost da proxyPort, tare da sunan mai masaukin daban daga tsarinsa da tasharsa. Saita su kafin connector.start(). Don ƙarshen HTTP na jama'a, waɗannan filaye biyu suna ɗaukar adireshi da tasha daga jerin proxy na HTTP.

Wannan yana ɗauka cewa mataimakin da aka tura shi ne ƙarin Apache da aka ambata. Hakanan yana iya samun tsoffin ƙima daga JVM http.proxyHost da http.proxyPort; bayyanannun ƙimar mahalli suna sa ƙarshen wannan hanyar a bayyane.

Misalin yana cin jikin rubutun, yana sakin albarkar kuma yana dakatar da hanyar. Amfanin yawo dole ne kuma ya cinye ko ya saki wakilcinsa domin a iya sakin haɗin da aka tara.