Ngesakhi se-HTTP se-Camel, beka i-proxy yangaphambili endaweni yokugcina yomkhiqizi owenza isicelo esiphumayo. Ku-Camel 4.18, ingxenye ye-RouteBuilder ingasebenzisa:

from("direct:status")
    .to("https://service.example.net/status"
        + "?proxyHost=proxy.example.net"
        + "&proxyPort=8080"
        + "&proxyAuthScheme=http");

I-URL yesevisi iseyindawo okuyiwa kuyo. Ukuze kube novivinyo lwe-API yomphakathi oluvunyelwe ngaphandle kokuqinisekisa i-proxy, umuntu ofanelekile ovela kuhlu lwe-proxy ye-HTTP angahlinzeka ngomsingathi nechweba lomlamuli. proxyHost ne-proxyPort zikhomba umlamuli; proxyAuthScheme ikhetha iphrothokholi esetshenziselwa ukuxhuma kuwo. I-proxy ye-HTTP ingadlulisa isicelo se-HTTPS ngomhubhe.

Sebenzisa izibambi zendawo zezakhiwo zamanani ahlukile ngokokusatshalaliswa. Uma kudingeka ukuqinisekisa i-proxy, isakhi siletha izinketho ezihlukene ze-proxyAuthUsername, proxyAuthPassword nendlela yokuqinisekisa. Ukuqinisekisa kwesevisi kusebenzisa ezinye izinketho.

Lokhu kulungiselelwa kungokwe-camel-http. I-CXF conduit ilungiselela iklayenti le-CXF; ayilungiseleli umkhiqizi we-HTTP ngenxa nje yokuthi umzila unamakhomponenti ahlobene ne-SOAP. Ngokufanayo, i-ProducerTemplate ithumela endaweni yokugcina futhi ayithathi indawo yokulungiselelwa kokuthutha kwaleyo ndawo.

Izilungiselelo ezisezingeni lesakhi zinganikeza okuzenzakalelayo okwabiwe. Izilungiselelo ezisezingeni lendawo yokugcina zigcina umzila othile ucacile.

Izihloko ezihlobene